Investigate running concurrent AppHosts with the same devtunnel IDs

The dev tunnels hosting integration defaults to creating dev tunnels with a generated tunnel ID that's based on the tunnel resource name and AppHost SHA, which in turn is based on the file path of the AppHost project file. The tunnel ID can also be manually set to a fixed value.

If multiple AppHost project instances using the same tunnel IDs are run concurrently, resulting in multiple tunnel hosts running for the same tunnel ID, what is the behavior? Is it supported by the dev tunnels CLI/service? If it is, how is traffic routed between the multiple hosts? Is it something that results in behavior we want in the context of Aspire.