Avoid unnecessary containers in Aspire.Hosting.Testing.Tests

[ReubenBond]

Description

This PR removes unnecessary containers from the Aspire.Hosting.Testing.Tests suite.

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
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

[Copilot]

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (4)

tests/Aspire.Hosting.Testing.Tests/TestingBuilderTests.cs:129

• [nitpick] Ensure that the new connection string check covers all necessary cases and does not introduce any unintended side effects.

var connectionString = await app.GetConnectionStringAsync("cs");

tests/Aspire.Hosting.Testing.Tests/TestingBuilderTests.cs:149

• The removal of the Redis container check might affect tests that rely on it. Ensure that all affected tests are updated accordingly.

Assert.Contains(appModel.GetContainerResources(), c => c.Name == "redis1");

tests/TestingAppHost1/TestingAppHost1.AppHost/Program.cs:28

• The removal of AddPostgres("postgres1") could cause issues if the PostgreSQL container is still required.

builder.AddPostgres("postgres1");

tests/Aspire.Hosting.Testing.Tests/TestingFactoryTests.cs:20

• The change from async to sync in HasEndPoints might affect the test's correctness. Verify that the test does not require async operations.

public void HasEndPoints()

[ReubenBond]

Note that the next test already exercises the GetConnectionStringAsync method