Improve performance of ContainerRegistry repositories by caching token

[adityapatwardhan]

PR Summary

This pull request introduces caching for container registry access tokens in the ContainerRegistryServerAPICalls class to avoid unnecessary repeated retrievals. The main changes focus on improving performance and reducing redundant network calls by storing and reusing the access token during the object's lifetime.

Container registry access token caching:

• Added a private field _cachedContainterRegistryToken to store the access token for reuse.
• Initialized the cached token to null in the constructor to ensure a fresh start for each instance.
• Updated GetContainerRegistryAccessToken to check for and return the cached token if available, logging a verbose message when the cache is used.
• After successfully retrieving a new access token, the method now stores it in the cache and logs a verbose message.

PR Context

In local testing, the improvement in performance for find with wildcard improved by 88% and install with dependencies improved by 83%

NOTE: We create a new instance of ContainerRegistryServerAPICalls for each invocation of any cmdlet. The cache is only shared within a single cmdlet invocation.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Documentation needed
    • Issue filed:
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and enumerated concerns in the summary.

[adityapatwardhan]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[anamnavi]

LGTM