Fix `RegexUtil` comments mode bug and `RegexUtilFuzzTest` setup (#32313)

### Description

Fixes for `RegexUtil`, which backs all regex-valued flags such as `--remote_download_regex`, and for its fuzz test:

* **Comments mode bug:** The `.*suffix` optimization appends `\z` to the suffix and uses `find()`. If the suffix enables comments mode via an inline `(?x)` flag, a `#` starts a comment that swallows the `\z`, so that e.g. `.*(?x)foo #comment` matched `foobar`. Such regexes now fall back to `Matcher#matches()`.
* **Fuzz test without coverage feedback:** rules_fuzzing 0.6.0 uses Jazzer 0.24.0, which can't instrument Java 25 class files ("Unsupported class file major version 69"). Since Bazel is compiled with Java 25, `RegexUtilFuzzTest` ran without any coverage feedback and its corpus never grew beyond a single input. rules_fuzzing 0.8.0 uses Jazzer 0.28.0, which supports Java 25. All of rules_fuzzing's dependencies already resolve to newer versions, so nothing else changes.
* **Fuzz test timeouts:** `java.util.regex` can take exponential time on fuzzer-generated regexes, which ended runs with a timeout after a few minutes, both in the original regex and in the optimized matcher. The haystack length is now capped at 16 characters (the optimized matcher can't be bounded directly and may use `find()`, which retries at every position) and inputs for which the original regex exceeds a budget of character accesses are skipped.

### Motivation

Found while working on #32287. `RegexUtilFuzzTest` is tagged `manual` and thus neither built nor run on CI, which is how the Jazzer incompatibility went unnoticed.

### Build API Changes

No

### Checklist

- [x] I have added tests for the new use cases (if any).
- [ ] I have updated the documentation (if applicable).

### Release Notes

RELNOTES: None

Closes #32313

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/bazel/pull/32313 from fmeum:ccr-a098070d-9za8in-regex-fuzz-fixes d51319ee49447c9b604df5d8bbc7f66cc0d62146
PiperOrigin-RevId: 1023243222
Change-Id: Ie226225cfe5fc582010d1f2dab714173753ea6b5
7 files changed
tree: d4a36a9d2638f1b63f5e0a8c1b6feffd5155807c
  1. .bazelci/
  2. .devcontainer/
  3. .gemini/
  4. .github/
  5. docs/
  6. examples/
  7. scripts/
  8. src/
  9. third_party/
  10. tools/
  11. .bazelrc
  12. .bazelversion
  13. .gitattributes
  14. .gitignore
  15. AGENTS.md
  16. AUTHORS
  17. bazel_downloader.cfg
  18. BUILD
  19. CHANGELOG.md
  20. CODE_OF_CONDUCT.md
  21. CODEOWNERS
  22. combine_distfiles.py
  23. combine_distfiles_to_tar.sh
  24. compile.sh
  25. CONTRIBUTING.md
  26. CONTRIBUTORS
  27. distdir.bzl
  28. extensions.bzl
  29. LICENSE
  30. maven_install.json
  31. MODULE.bazel
  32. MODULE.bazel.lock
  33. oneversion_allowlist.csv
  34. oneversion_allowlist_for_tests.csv
  35. pyproject.toml
  36. README.md
  37. repositories.bzl
  38. requirements.txt
  39. SECURITY.md
  40. verify_module_bazel_lock.sh
README.md

Bazel

{Fast, Correct} - Choose two

Build and test software of any size, quickly and reliably.

  • Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.

  • One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.

  • Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.

  • Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.

Getting Started

Documentation

Reporting a Vulnerability

To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.

Contributing to Bazel

See CONTRIBUTING.md

Build status