Get FirstPartyUsage Tagged IP for RP VMSS and GWY VMSS

[preetisht]

Which issue this PR addresses:

https://issues.redhat.com/browse/ARO-20272

• VMSS IP Tags for both RP and Gateway
• Unified Configuration (vmssIpTags, vmssIpTagsDisabledRegions)
• ARM Conditional Logic to apply empty ipTag for disabled regions
• Edge Case Handling (empty arrays, missing config)
• Configuration picked up from RP-Config

Fixes

What this PR does / why we need it:

https://issues.redhat.com/browse/ARO-16025

This is a part of Microsoft Security Wave 5 fix. All our PublicIP's for both MSIT and AME environment for ARO Classic shoudl have FirstPartyUsage tags .

This PR implements IP tags support for Azure Red Hat OpenShift Virtual Machine Scale Sets (VMSS) to comply with Microsoft Security Wave 5 requirements. The implementation adds unified configuration parameters (vmssIpTags, vmssIpTagsDisabledRegions) that enable region-specific IP tagging for both RP and Gateway VMSS public IPs, with ARM template conditional logic that gracefully handles disabled regions by deploying empty IP tags arrays. The solution has ARM conditionals logic and includes edge case handling for missing or empty configuration scenarios.

Test plan for issue:

• make test.go passes all the test.
• Deployed in Canary eastus2euap. Post deployment verify if the new VMSS instances both RP and GWY have proper tagged IP's.
• Create a cluster in Canary and check if the cluster is sending metrics to geneva.
• Log into both RP-VMSS and GWY-VMSS instance and check if some of the critical endpoints are accessable .

Is there any documentation that needs to be updated for this PR?

• A doc will be created on how to deploy in regions where we do not FirstPartyUsage tags has not yet been provided to us by Microsoft .
• We will create a TSG which will be a part of another PR which will be related to monitoring of our Public IP's which does not have a FirstPartyUsage Tag .

How do you know this will function as expected in production?

• We will do an extensive tests in Canary region and updated all our test cases and results in JIRA .
• All the artifacts are uploaded and JIRA commets updated .