Add info back into configuration

[leuyentran]

Change Overview

Add non-mandatory Azure information back into config structure. The purpose of such change, is to bring back information regarding Azure config such as AZURE_RESOURCE_MANAGER_ENDPOINT , AZURE_AD_ENDPOINT, AZURE_AD_RESOURCE, and AZURE_CLOUD_ENV_ID to callers and eventually end-users.

The end goal is to have all Azure config information will be available to end-user.

Pull request type

Please check the type of change your PR introduces:

• 🚧 Work in Progress
• 🌈 Refactoring (no functional changes, no api changes)
• 🐹 Trivial/Minor
• 🐛 Bugfix
• 🌻 Feature
• 🗺️ Documentation
• 🤖 Test

Test Plan

• 💪 Manual
  Manual test was ran downstream to ensure informations are being passed back
• ⚡ Unit test
  Was run as a sanity check. No unit test added nor changed since there was no functional change
• 💚 E2E

[github-actions]

Thanks for submitting this pull request 🎉. The team will review it soon and get back to you.

If you haven't already, please take a moment to review our project contributing guideline and Code of Conduct document.

[pavannd1]

Are the downstream callers being changed to use the config values from the map?

[leuyentran]

Are the downstream callers being changed to use the config values from the map?

@pavannd1 Downstream callers will store these information alongside with clientID, tenantID, clientSecret and other config information. At the moment, it it intended for information surfacing, i.e. showing end-user the complete suite of config being used for Azure Client. No data management functional changes.

[bathina2]

minor nit, will approve

[ihcsim]

LGTM.