Implement pagination for receiving MCR catalog items

[adityapatwardhan]

PR Summary

This pull request enhances the Azure Container Registry repository listing functionality by adding support for paginated API responses. The main improvement ensures that all repositories are retrieved, even when the server returns results across multiple pages. The most important changes are:

Pagination Support for Repository Listing:

• Modified FindAllRepositories to call GetHttpResponseJObjectUsingDefaultHeaders with a new usePagination parameter set to true, enabling paginated retrieval of repositories.
• Updated GetHttpResponseJObjectUsingDefaultHeaders to accept a usePagination flag and, when enabled, route requests through a new pagination-aware method. [1] [2]
• Introduced SendRequestAsyncWithPagination, which iteratively follows pagination links in the HTTP response headers (Link: ... rel="next") to aggregate all repository results into a single JObject.

Code Cleanup and Refactoring:

• Reorganized and deduplicated using directives at the top of ContainerRegistryServerAPICalls.cs for improved readability and maintainability.

PR Context

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).

[adityapatwardhan]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[adityapatwardhan]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[adityapatwardhan]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).