Virtual environment is applied automatically in all packages in a multi-root workspace

[connor4312]

Testing #457

1. Have multiple projects/a multiroot workspace
2. Have some of the projects using the default system environment
3. "Create Environment" and choose one of the projects to create the environment in
4. Quick Create
5. 🐛 it gets applied to all of them

[cwebster-99]

This is similar to the discussion we were having earlier, this was originally "as designed" that we favor a virtual environment in favor of a system python once one is present in the workspace. I think instead if an environment is created in a subfolder it should only be applied to that project. If the environment is created at the root we can apply to all. Let me know your thoughts though @eleanorjboyd

[eleanorjboyd]

Yes I like this as a decision

[cwebster-99]

🐛 in a multi project scenario where a virtual environment is already assigned to one project and the other is assigned to a global python. If you create a new virtual environment, it will apply to both projects. We should respect venv selection that exists currently and only assign a new venv to the project that has a global selection

[luabud]

I can no longer repro the original bug, so marking this issue as verified:
https://github.com/user-attachments/assets/0d7237fe-bc9e-4a45-b87c-7ee2e0b4cb64

However I am not able to get this behaviour:

we favor a virtual environment in favor of a system python once one is present in the workspace

So opened a separate issue for it: #595