Add an aspire logs [resource resource] command

[mitchdenny]

We would like the ability for developers, using the aspire CLI to be able to execute aspire logs [resource name]. This would result in the logs that would normally appear in the dashboard appearing in the console log.

The problem we need to solve is how does aspire logs [resource name] identify and connect to the apphost which is managing the resource.

At the moment we have an RPC mechanism where the aspire CLI itself listens of a connection on a unix socket (the apphost initiates the connection). Should we reverse the handshake here and connect the other way? Should each app host create a socket in a well known path which the CLI can use the find the right apphost?

What security concerns are there here?

[mitchdenny]

One thing we could do is have the AppHost write a file in a well known directory with metadata that the CLI can use. That metadata would have information such as where the project file is located, and what the path to the socket is.

If there are multiple apphosts running at once, then the CLI could actually prompt the user to ask which one to connect to (show the csproj path and the PID).

This could actually be useful for testing scenarios as well because if you have a hung test, you could use the aspire CLI to inspect the state (and DevKit extension / VS / other IDEs could enrich the experience too).