Add GetArgumentListAsync to resource extentions

[Alirexaa]

Description

This pull request introduces a new method to retrieve arguments from resources asynchronously and includes updates to the public API and tests to support this new functionality.

New Method for Argument Retrieval:

• Added GetArgumentListAsync method to ResourceExtensions to retrieve arguments from resources asynchronously. This method handles different types of arguments, including those provided by IValueProvider. (src/Aspire.Hosting/ApplicationModel/ResourceExtensions.cs)

Public API Update:

• Updated PublicAPI.Unshipped.txt to include the new GetArgumentListAsync method in the public API. (src/Aspire.Hosting/PublicAPI.Unshipped.txt)

Unit Tests:

• Added a new test GetArgumentListAsyncReturnCorrectArguments to verify that GetArgumentListAsync returns the correct arguments. (tests/Aspire.Hosting.Tests/ResourceExtensionsTests.cs)
• Introduced a DummyResource class implementing IResourceWithArgs for testing purposes. (tests/Aspire.Hosting.Tests/ResourceExtensionsTests.cs)

Fixes #6644 6644

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

Microsoft Reviewers: Open in CodeFlow

[eerhardt]

Are there any places in the current code that can be using this new API now? I see a bunch of places where we already have this logic. Especially in tests.

[Alirexaa]

Yes, there are. Do you want me to update those codes that use this new API or can I do this in another PR?

[eerhardt]

Please do it here. It adds extra validation to the API.

[eerhardt]

LGTM. Thanks for the contribution, @Alirexaa.

@mitchdenny @davidfowl - any concerns?

[davidfowl]

Yea I think we need to unify these methods (this and GetEnvironmentVariables async) with what happens at runtime. I'm guessing you're using this for testing, but it is missing some critical functionality that we added in 9.

aspire/src/Aspire.Hosting/Dcp/ApplicationExecutor.cs

Line 1398 in 109f7dd

var task = ExpressionResolver.ResolveAsync(isContainer, valueProvider, DefaultContainerHostName, cancellationToken);

[Alirexaa]

@davidfowl @eerhardt
I'm not familiar with those changes that were added in 9.
Could you edit my PR to capture those?