[10.0.0] Fix crash on Starlark rules named `genrule` (#31676) (#31698)

### Description
`Rule.outputsToBindir()` special-cases rules whose rule class is named
`genrule` and reads their `output_to_bindir` attribute. This check
didn't exclude Starlark rules, so analyzing any Starlark rule exported
as `genrule` crashed Bazel with:

java.lang.IllegalArgumentException: No such attribute output_to_bindir
in genrule rule //a:g

Restrict the special case to the native rule, matching the existing
`!ruleClass.isStarlark()` check in `ToolchainContextUtil`.

### Motivation

### 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 #31676


COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/bazel/pull/31676
from fmeum:ccr-3e4f2a29-vlgvys cba4c2cfddf4eca60d430fd79ceb57a3181034db
PiperOrigin-RevId: 996621986
Change-Id: I645e770ee230cb69c9a5c1c30262cfcced08aca9

Commit
https://github.com/bazelbuild/bazel/commit/d5ab4e5c0009ae2b4bf9a3f56d035f4ebf90120f

Co-authored-by: Fabian Meumertzheim <fabian@buildbuddy.io>
2 files changed
tree: d871b8ab7e74bb5ba46211e511512324eac0cb23
  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