Fix typo in doccomment in ContainerResourceBuilderExtensions.cs

[KuraiAndras]

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 #9341

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 (consider using one of the following templates):
      • New (or update) doc-idea template
      • New breaking-change template
      • New diagnostic template
  • No

Other information

Although it is doc related; this part of the docs is the API docs which are generated from this source if I understand correctly.

[Copilot]

Pull Request Overview

This PR fixes a documentation typo by updating the generic method syntax in the API doc comments for improved clarity and correctness.

• Corrected the usage of generic syntax from curly braces {} to angle brackets <> in doc comments.
• Ensures generated API docs accurately reflect proper usage patterns.

[Copilot]

Pull Request Overview

This PR fixes a typo in the doc comment of ContainerResourceBuilderExtensions.cs to ensure that the sample usage of generic methods correctly utilizes HTML-encoded angle brackets.

• Fixes generic type syntax in doc comments for clearer API documentation.

[davidfowl]

Thanks!