Spin off configuration schema generator as a standalone package

[pedropaulovc]

Autocomplete of Aspire configs in appsettings.json is fantastic as my project is growing. I would love to have this capability in my projects as well. Also, I'm using keyed component resolution and the default Aspire schema doesn't know what's the key I'm using in my code. Looks like this capability is handled by the configuration schema generator introduced in #1383 . The team should consider spinning off this capability as an extension package for 3P usage.

[davidfowl]

This is the plan right @eerhardt?

[eerhardt]

This is the plan right @eerhardt?

Yes, we will need to do something here if we want to build Aspire Components outside of the dotnet/aspire repo.

[aaronpowell]

We're wanting to use this in the Community Toolkit (tracking CommunityToolkit/Aspire#112), what would be required to ship this as a .NET CLI tool that we could use, even if it was on a package feed other than nuget.org.