blackbox workspace tests need a complete overhaul for maintainability

[aiuto]

The set of tests under src/test/j.c.g/devtools/build/lib/blackbox is brittle and hard to maintain.

• They depend on external repositories. So either have to keep those in sync with versions in //WORKSPACE or risk version skew.
  • we are not necessarily sharing the download cache with the main repo
  • version numbers and sha sums are embedded in java code.
  • the workspace rules are getting increasingly complex, where dependencies have to use deps patterns to download their deps
    • This degenerated in Update blackbox tests to use rules_pkg instead of built-ins for pkg_tar #9046 to needing to have a big workspace preamble in any test which uses the RepoWithRuleWriting pattern.
• They dynamically generate content of WORKSPACE files which then are consumed in the same test
  • this is had to debug if you get the workspace rules wrong. These files could be generated by a BUILD rule and be data input to the tests.

Some suggestions:

• Replace the use of rules_pkg in the framework with a bazel source internal tar packager. Provide a tiny tar utility for use in tests #11183
• Restructure the tests so we can inspect the intermediate artifacts more easily.

[github-actions]

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

[github-actions]

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team (@bazelbuild/triage). Thanks!