Only rebuild / restart impacted resources when hot reload cannot be used (while debugging)

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Is your feature request related to a problem? Please describe the problem.

When debugging and a code change cannot be hot reloaded, it requires a rebuild/restart of the entire Aspire application, but it would be more productive to only rebuild/restart the impacted projects.

### Describe the solution you'd like

To start this off, I appreciate that this is no small ask (to put it mildly) and that it likely larger than the Aspire / ASP.NET teams (i.e. involving the VS team). However, I do feel like it would be a great feature if its achievable.

Let's say I have the following:

* AppHost
* ServiceDefaults
* Class library "A"
* Web project "B" (depends on "A" + ServiceDefaults)
* Web project "C" (depends on ServiceDefaults)

If I start-with-debugging and change something that cannot be hot reloaded in "C", theoretically the service could be stopped, rebuilt, and restarted without having to rebuild/restart the app host and all of the other projects.

Admittedly, dependencies make this even more complex (changes to "A" rebuilds/restarts "B" but not "C", changes to "ServiceDefaults" rebuilds/restarts all projects but not AppHost, etc) but the resulting developer experience improvements would be fantastic.

### Additional context

To avoid this being closed as a duplicate, I want to clarify how this issue differs from several existing ones:

#295 Involves the developer manually stopping/starting services. This issue is about Visual Studio working with Aspire to automate the stop/rebuild/start cycle of impacted projects _only_.

#923 Involves keeping specific resources running after shutdown, with a specific focus on containers and/or other "not my code" resources.