Publishing Bazel rules that depend on tools: take 2

In this detailed account, the author explains the process and challenges faced while adapting a pattern for publishing Go binaries from the bazel-lib repository to the rules_py repository, which involved transitioning from Go to Rust for tool development. The shift was motivated by the desire to leverage open-source work in the Python ecosystem but encountered difficulties due to differences in cross-compilation support between Go and Rust. The solution involved using GitHub Actions to automate the building of binaries, integrating integrity hashes into the release artifacts, and modifying the release process to be more streamlined and less reliant on manual maintenance. Key features of the release process include the exclusion of non-essential files to prevent bloating, stamping release tags into source files, and ensuring that pre-built binary toolchains are fetched efficiently for users. The process is designed to be reproducible and maintainable, ensuring that releases can be easily managed by a small team. The author emphasizes the importance of a streamlined process for ensuring a seamless end-user experience and mentions future updates as the rules_py project approaches its 1.0 release.