Improvements when working with devcontainers/codespaces via VSCode

[gabynevada]

Hi! I'm sharing some issues that we're facing while using aspire in devcontainers via VSCode, hopefully we can get workarounds or to consider for new features in the project.

1. Allow auto sharing of all the ports of services defined by resources in their endpoints

Right now only the dashboard and some of the ports used to communicate are auto shared, if I have resources like databases, apis with swagger documentation, database management tools like pgweb then I need to manually share the ports to get them to work from my machine.

Possible solution could be to share every port listed in the endpoints column for the resources in the app host:

Port sharing could be done using a custom method or the built-in method of printing the urls in the console as defined in https://docs.github.com/en/codespaces/developing-in-a-codespace/forwarding-ports-in-your-codespace

2. Allow specifying a launch profile from vscode launch.json

The current recommended way of launching a debug session from the AppHost using vscode launch.json does not support specifying a launchSettings.json profile, the usecase for this is to launch the app host using http in development as it's easier than setting up the development certificate using a devcontainer.

Current launch.json

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "MyApp.AppHost",
      "type": "dotnet",
      "request": "launch",
      "preLaunchTask": "build",
      "projectPath": "${workspaceFolder}/apps/MyApp.AppHost/MyApp.AppHost.csproj"
    }
  ]
}

Proposed solution would be to allow the launchSettingsProfile setting and the ** launchSettingsProfile** that the clr launch configuration currently allows. Reference