Support a new launch profile type to launch the project in a container

[baronfel]

Is your feature request related to a problem? Please describe.

The CLI doesn't have a native ability to run a project inside a container, while Visual Studio and Visual Studio Code do via Docker tools plugins for those respective editors. We should expand this support to the CLI via a new launch profile launch type, so that the intent to use a container can be uniformly expressed. Then any tooling that wants to launch a project as a container natively could interpret this launch profile type and map that to whatever mechanism of action was correct for that environment.

Describe the solution you'd like

We should define a new launch type that directs the host to create a container for the project in question, then executes it. This launch profile should be able to control key aspects of the container execution, including:

• container engine to use
  • (docker/podman/other - our current default is docker)
• arguments to provide to the application
  • optionally - completely overriding the entrypoint?
• environment variables to specify when the container runs
• volume mounts to create when the container runs
  • useful for config, secrets, etc
• ports to map when the container runs
  • if not specified, the host could map to random available ports

References

• Original request came from Support running and debugging Aspire service projects in Containers aspire#969

cc @DamianEdwards @davidfowl @danegsta

[marcpopMSFT]

Team Triage: Marking for 9 for now but it'd be good to understand prioritization here. Additionally, launch profiles were originally a web-focused feature and who would do this work as a bit nebulous. CC @vijayrkn for his thoughts around launch profiles going forward.

[Cjewett]

Just wanted to double check if this was still targeted for .NET 9? I know I've seen some other repositories start pausing additional feature additions in preparation of launch.