Updating configuration for a symantec version promote and publish

[nikhil2611]

Description

Updating configuration for a symantec version promote and publish
Also updated the HAB_BLDR_CHANNEL to the plan files.

Related Issue

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

• I have read the CONTRIBUTING document.
• I have run the pre-merge tests locally and they pass.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
• All new and existing tests passed.
• All commits have been signed-off for the Developer Certificate of Origin.

[johnmccrae]

I overlooked something earlier. We need an 18-Stable branch for this because we'll need to manage chef-18 and the omnibus style builds for a while. Can you please create that branch before you merge?

[nikhil2611]

I overlooked something earlier. We need an 18-Stable branch for this because we'll need to manage chef-18 and the omnibus style builds for a while. Can you please create that branch before you merge?

Created a branch (18-Stable) out of main before this PR merge - https://github.com/chef/fauxhai/tree/18-Stable