[Self-filed] Switch back to rules_python when their issues are fixed

[cpsauer]

We'd switched to rules_python to get a hermetic python interpreter and to be able to make sure that everyone was on the same python version, rather than relying on system python. However, a number of issues caused us to revert for now.

Please see

• https://github.com/hedronvision/bazel-compile-commands-extractor/issues/163
• https://github.com/bazelbuild/rules_python/issues/1732
• https://github.com/hedronvision/bazel-compile-commands-extractor/issues/165
• (rules_python issue to come)
• https://github.com/hedronvision/bazel-compile-commands-extractor/issues/166
• https://github.com/bazelbuild/rules_python/issues/1169

[cpsauer]

[Intentional blank comment, added to make it clear from the table view that this isn't a user issue lacking a response.]

[cpsauer]

Blocks https://github.com/hedronvision/bazel-compile-commands-extractor/issues/148

[peakschris]

There is also rules_py that is worth a look: https://github.com/aspect-build/rules_py

[peakschris]

I became very disillusioned with the state of python within the bazel ecosystem, and took the step of rewriting from Python to Go for a number of our internal tools. The go build can be isolated inside the module, with go binaries published by your CI. For users, the repo then fetches this on demand, so there is no leakage of go tooling outside the module.

I didn't know go, but AI can rewrite python to go remarkably well. I imagine this approach works equally well with Rust. @alexeagle wrote about this: https://blog.aspect.build/releasing-bazel-rulesets-rust