[Bug]: running venv python directly no longer possible

[AlexanderLanin]

What happened?

After invoking py_venv it was previously possible to run .venv/bin/python my_script.py.
With recent versions this fails, as python must be activated first.

I simply tried our py_venv invocation with a bunch of versions, see below.

Version

Development (host) and target OS/architectures:

Output of bazel --version: bazel 8.3.0

Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file:

1.4.0 - ok
1.5.0 - yanked
1.5.1 - fails as it requires rust
1.5.2 - some python conflict/resolution error
1.6.0 - error, does not support venv-name param
1.6.1 - error, does not support venv-name param
1.6.2 - builds, but .venv/bin/python cannot be run without activation
1.6.3 - builds, but .venv/bin/python cannot be run without activation

Language(s) and/or frameworks involved:

How to reproduce

Use anything with a py_venv target

Any other information?

No response

[arrdem]

Addressed by #629.

Dupe of #594.