Add license interceptor in automate gateway (#8439)

[YashviJain01]

• Adding the intercerptors with error only for license

• Removing the function, will create another PR for this

• Removing interface, will create another PR for this

• Adding the function for interceptor

• Adding interceptor layer for license

• Adding allow api list if the license needs to be applied from backend

• Adding license apply

• Adding license function in default deploy

• Removing unwanted loggers

• Adding license apply command in pipelines, and adding create token api in api allow list

• Applying license at various location to unblock the pipeline

• Adding changes

• Adding Applying license in do_dploy for chef server

• updating the temp license

• Adding A2_license as a variable from vault

• Adding A2_license as a environment variable

• Adding A2 license in the pipeline

• Adding license in studio pipelines

• Adding license data

• Adding license data

• Adding license data

• Adding license

• Adding licrnse in dev from command

• Adding license from vault and applying it

• Adding license in gateway intergation

• Adding license in gateway intergation

• Adding license key in the pipeline

• Adding license after upgrade

• commenting jq line for print

---

🔩 Description: What code changed, and why?

⛓️ Related Resources

👍 Definition of Done

👟 How to Build and Test the Change

✅ Checklist

All PRs must tick these:

• I have read the CONTRIBUTING document.
• All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

• Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
• Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
• Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
• Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
• Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

• Tests added/updated? (all new code needs new tests)
• Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.

📷 Screenshots, if applicable

[netlify]

👷 Deploy Preview for chef-automate processing.

Name	Link
🔨 Latest commit	883f1a1
🔍 Latest deploy log	https://app.netlify.com/sites/chef-automate/deploys/669a61911f1b8a0008abd233

[sonarqube-for-infrastructure-prod]

SonarQube Quality Gate

27.2% Coverage on New Code (is less than 80%)

See analysis details on SonarQube

[sonarqube-for-infrastructure-prod]

Quality Gate failed

Failed conditions
6 New issues
26.6% Coverage on New Code (required ≥ 80%)
5.1% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube

Catch issues before they fail your Quality Gate with our IDE extension SonarLint