Description
In Aspire 9.2 we introduced a behavior where unmatched parameters from the aspire run and aspire publish commands get passed through to the underlying dotnet run -- <unmatched parameters>. Developers can choose how they bind these command-line args. Potentially they could bind them to the .NET config system.
However, we also want to support interactive prompting if parameters are not supplied. To make this work we probably want to have an approach where the CLI calls into the apphost across the RPC before it starts running/publishing and asks it to make calls back the other way to prompt for parameters.
We would start of simple and just prompt for strings and stuff the values in configuration, but we'll eventually want to add metadata that supports things like presenting options etc.
The initial call to the apphost will not return until the apphost is satisfied that it has all the parameters.