[tests] use test container registry in WaitFor hosting tests

[radical]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue:
  • No

Microsoft Reviewers: Open in CodeFlow

[radical]

Adding this for the hosting tests would be useful - (

aspire/tests/Aspire.Playground.Tests/Infrastructure/DistributedApplicationTestFactory.cs

Lines 57 to 77 in 23fdf31

	internal sealed class ContainerRegistryHook : IDistributedApplicationLifecycleHook
	{
	public const string AspireTestContainerRegistry = "netaspireci.azurecr.io";
	public Task BeforeStartAsync(DistributedApplicationModel appModel, CancellationToken cancellationToken = default)
	{
	var resourcesWithContainerImages = appModel.Resources
	.SelectMany(r => r.Annotations.OfType<ContainerImageAnnotation>()
	.Select(cia => new { Resource = r, Annotation = cia }));
	foreach (var resourceWithContainerImage in resourcesWithContainerImages)
	{
	string? registry = resourceWithContainerImage.Annotation.Registry;
	if (registry is null || registry.Contains("docker.io"))
	{
	resourceWithContainerImage.Annotation.Registry = AspireTestContainerRegistry;
	}
	}
	return Task.CompletedTask;
	}
	}