Start Configuration of Python Gazelle

[michael-christen]

Changes:

• Establish a mechanism for defining external python requirements via a requirements.in, generating updates to a lock file with bazel run //:requirements.update
• Configure gazelle python and protobufs
• Configures via gazelle directives to use a file based approach, stick with the BUILD configuration, disable go, default visibility to private and resolve py imports
• Update dev_setup to install openjdk (java), tree, ranger, ag

New Commands:

bazel run //:requirements.update
bazel run //:gazelle_python_manifest.update
bazel run //:gazelle

New Tests:

//:requirements_test
//::gazelle_python_manifest.test

Notes:

• One of the recurring issues I have every time I deal with updating WORKSPACE is slight incompatibilities with various repos that result in incomprehensible output errors.
• stackb/rules_proto is one of the only things that seems to support what I'm looking for, and while it is getting steady contributions hasn't pubilshed a release in about a year. https://github.com/rules-proto-grpc/rules_proto_grpc. Additionally, it could be handy to look into what it would take to make my own "shitty" version of these rules to learn more about what's going on in gazelle's / bazel's internals
• bzlmod migration didn't go well for me, most tutorials out there still use WORKSPACE, might be good to look into in the future / figure out how to migrate piecemeal, but bypassed this and 7.0.1 bazel upgrade for now

Related Issues:

• Noting the issue with requiring a gazelle directive for proto libraries: [Gazelle][proto] How to automatically resolve protobuf target bazelbuild/rules_python#1703
• fix: Fix per-file config interaction with one py_binary per main bazelbuild/rules_python#1664 fixes the reason I had to "disable" my py_binary, wait for that to release and then update. I could probably patch this in, but don't quite know how 🤷
• Sounds like there's some talk around gazelle c++ How use bazel-gazelle in cpp project? bazel-contrib/bazel-gazelle#910
• I'm helping ;) docs: Update gazelle/README.md to fix package_name formatting bazelbuild/rules_python#1712 (doc update)

References:

• https://github.com/bazelbuild/bazel-gazelle
• https://github.com/stackb/rules_proto
• https://github.com/bazelbuild/rules_python/tree/main/gazelle

Future Things to Look Into:

• Setup a gazelle test that checks output of //:gazelle -- -mode diff is zero
• Configure rust with gazelle: https://github.com/Calsign/gazelle_rust
• A really cool / general parser / generator (what github uses for "semantic" tool): https://tree-sitter.github.io/tree-sitter/ Could use to make small code generator / modification? Or maybe more general utilities?
• General compile command completion: https://github.com/hedronvision/bazel-compile-commands-extractor
• Maybe play with https://github.com/rules-proto-grpc/rules_proto_grpc as an alternative to stackb
• If I can't use gazelle for some things, mess around with https://github.com/bazelbuild/buildtools/tree/master/buildozer

[michael-christen]

Scrub XXXs a little, define test commands, update README for changing requirements, etc.