Allow wildcard for MAR repository for FindAll and FindByName

[adityapatwardhan]

PR Summary

This pull request to src/code/ContainerRegistryServerAPICalls.cs includes changes to enhance the functionality of finding packages in a container registry and improve the test coverage for the MAR repository. The most important changes include adding a new URL template for listing repositories, modifying the FindAll and FindNameGlobbing methods to use the new FindPackages helper method, and adding new tests for wildcard searches.

Enhancements to finding packages:

• Added a new URL template containerRegistryRepositoryListTemplate for listing repositories.
• Modified the FindAll method to use the new FindPackages helper method instead of returning an error.
• Modified the FindNameGlobbing method to use the new FindPackages helper method instead of returning an error.
• Added a new helper method FindAllRepositories to list all repositories in the container registry.
• Added a new helper method FindPackages to find packages using wildcards and handle MAR-specific logic.

Improvements to test coverage:

• Added new tests to verify finding resources with wildcards in their names and finding all resources in the MAR repository.

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.

[anamnavi]

Left some feedback, but overall looks good!