aspire add --version should not prompt for a version

[sebastienros]

The CPM test started failing because it's now prompting for which version of Aspire.Hosting.Redis it should pick, but the command line explicitely mentioned it

[eerhardt]

@mitchdenny

[Muckenbatscher]

The interactive flow will only be skipped if the CLI supplied version of the integration was found in one of the channels.

The CLI command dotnet package search Aspire.Hosting.Redis --take 1000 --skip 0 --format json will only return the latest version of each of the packages for a given source.
To search for all versions of a specific package the flag --exact-match needs to be specified.

The current flow is to get all package names to be able to also perform a fuzzy search via LINQ. The check for the CLI provided version number could be performed for the best candidate package name. Or it could be skipped entirely and just be passed directly to dotnet package add --version without any validation (other than the dotnet package add command failing for any non-existing version).