Exported `VIRTUAL_ENV=...` results in warnings

[Ravencentric]

After #194, setup-uv now exports the env var VIRTUAL_ENV. The top level project API (e.g., uv sync) does not respect this and emits the following warning:

warning: `VIRTUAL_ENV=.venv/bin` does not match the project environment path `.venv` and will be ignored` upon invocation.

I understand the reasoning behind the change, but I think it should be opt-in rather than the default.

[eifinger]

VIRTUAL_ENV should be set to .venv instead of .venv/bin. This is a bug.

Can you explain, why you think this should be opt-in?

[Ravencentric]

Just to avoid the warnings. If they can be avoided while still unconditionally setting VIRTUAL_ENV=... then I have no strong opinion either way.