[helly25]

Future bashtest releases will submit BCR tests for Bazel 8.x and 9.x, matching the registry support decision already applied to 0.7.1. This prevents the next automated publication from restoring the Bazel 7 test lane.

AG;DR

• Remove only 7.x from .bcr/presubmit.yml; keep Bazel 8.x/9.x, all six platforms, and all build/test targets unchanged.
• Document the BCR template separately from repository CI. The GitHub test matrix is unchanged; there is no separate BCR MODULE.bazel template to edit.
• Start development version 0.7.2 in MODULE.bazel and CHANGELOG.md because the mandatory version-consistency hook requires the first post-release commit to advance beyond the latest 0.7.1 tag. The README continues to advertise the released 0.7.1 version. This does not publish another release.
• The immutable 0.7.1 tag and release archive, and BCR publication PR #11489, are unchanged by this PR.
• Validation: bazel test //... passed (19 passed, one Windows-only test skipped on macOS), and pre-commit run --all-files passed. Current-head CI run 41220138490, attempt 2 passed all nine OS/Bazel matrix cells, pre-commit, release-site verification and the final gate. The initial macOS Bazel 8 job encountered an existing SIGKILL test cleanup PermissionError; a targeted job retry passed without a source change.