Running multiple "dotnet watch run" with dependency overlap periodically fails

### Description

Referencing this issue opened in aspnetcore: https://github.com/dotnet/aspnetcore/issues/33827

Forgive me if I'm opening the issue in the wrong place, but it seems like an issue with `dotnet watch` would fall under the dotnet runtime and not aspnetcore. I hope that is the actual reason the issue was closed in aspnetcore because the reason given for closing doesn't seem valid to me. And this issue seems like a real issue with `dotnet watch` as it prevents a valid workflow in a complex workspace.

It seems that `dotnet watch` does not support being run on an entire solution.

So in a complex workspace, we must run multiple dotnet projects at the same time using `dotnet watch run` on each project. But if they have shared dependencies they can step on each other's toes and cause CS2012 - "Cannot open 'file' for writing".

As the issue author says in the linked issue, *nix systems run into CS2012 much less often but on Windows it is very annoying.

For more detail, please reference the linked issue above.

### Reproduction Steps

For more detail, please reference the linked issue above.

### Expected behavior

I expect to be able to either run `dotnet watch` on a solution or run it on multiple projects with shared dependencies and not run into CS2012.

### Actual behavior

Frequent occurrences of CS2012

### Regression?

_No response_

### Known Workarounds

For more detail, please reference the linked issue above.

### Configuration

_No response_

### Other information

_No response_