uv

bacde427 - Fix `uv venv` handling when `VIRTUAL_ENV` refers to an non-existant environment (#4073)

Fix `uv venv` handling when `VIRTUAL_ENV` refers to an non-existant environment (#4073) Closes https://github.com/astral-sh/uv/issues/4072 This was an accidental change in https://github.com/astral-sh/uv/pull/4029 in which I had updated the pull request to support virtual environments as requested in review and forgot to revert it. Separately, we shouldn't fail if `VIRTUAL_ENV` points to an empty directory and `SystemPython::Allowed` is used, will address that separately.