Go upgrade, Azure SDK upgrade with azure api scan filtering enabled

[vivekshankar1]

🔩 Description: What code changed, and why?

In azure API scan we were not able to filter subscriptions. Lets say if any user has 1000 subscriptions and they want to run scans for some particular subscriptions it wasn't possible earlier. This change used the latest version of Azure SDK which helps us to gets the tags. We have added some filtering logic that can be used to choose particular subscriptions out of many. Scans will also use the chosen filters
To make this possible, we had to update Azure sdk, that relies on go 1.15 or more, so we had to update go version too. Pr also contains fix for common name support in certificate which requires env GODEBUG=x509ignoreCN=0 to be set to support legacy certificates.
Azure filtering and scanning supports wildcard matches too.

⛓️ Related Resources

• Go upgrade to latest version - 1.15 #5801
• Filter Azure Subscription ID in the UI #5677

👍 Definition of Done

• All services should build properly
• Go version should be upgraded to 1.15
• We should be able to filter subscriptions by name, tags
• Compliance scans should run using those selected filters

👟 How to Build and Test the Change

STEP 1
inside the hab studio

[default:/src:0]# build components/automate-ui-devproxy/
[default:/src:0]# start_automate_ui_background
[default:/src:0]# start_all_services
[default:/src:0]# rebuild components/automate-scaffolding-go/
[default:/src:0]# local_scaffolding_origin=<your-username> rebuild components/nodemanager-service

STEP 2
open new window
go to automate UI path

$ cd components/automate-ui
and run the command 

npm run serve:hab

✅ 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.)
• [x ] 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

Screen.Recording.2021-10-13.at.12.45.00.AM.mov

[netlify]

👷 Deploy Preview for chef-automate processing.

🔨 Explore the source changes: 95c6e1a

🔍 Inspect the deploy log: https://app.netlify.com/sites/chef-automate/deploys/6176f990e5870d00075fde77

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
5 Code Smells

9.8% Coverage
0.0% Duplication