Enable Aspire MCP server on GitHub Coding Agent

The way the GitHub coding agent works is that when a workflow starts it spins up all of the MCP servers and enumerates the tools that are available to them. The approach we are taking with the MCP server being hosted in the dashboard may be incompatible with this.

We need to be able to launch an MCP server via the Aspire CLI and then proxy those requests to the dashboard once it is available (this MCP server may need to be able to work with multiple apphosts).

This might also help solve the issue with self-signed certificates in VSCode because the `aspire mcp` server could potentially have an `stdio` mode.