[13.3] `aspire run` on an already running app host doesn't stop existing cli session gracefully

[afscrome]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

If you run aspire run a second time, it stops the existing app host instance before starting a new instance up.

When you do this, it closes the existing CLI, which complains about an unexpected error occurring. aspire stop on the other hand causes the CLI to stop more gracefully,

Running another instance with aspire run

Expected Behavior

If you stop the app host via aspire stop, the cli session exits gracefully. I'd expect a restart from aspire run to behave the same way.

Steps To Reproduce

1. In one terminal session run aspire run
2. In a second terminal session, run aspire run for the exact same app host.

Exceptions (if any)

No response

Aspire doctor output

No response

Anything else?

No response

[joperezr]

I believe this is a dupe of #16568 which @danegsta is already working on in the DCP side.