[py][build] Update bazel rules_python

[cgoldberg]

💥 What does this PR do?

Bump bazel rules_python to 2.0.1 (no toolchain version upgrades in this release)

🤖 AI assistance

• No substantial AI assistance used
• AI assisted (complete below)
  • Tool(s):
  • What was generated:
  • I reviewed all AI output and can explain the change

🔄 Types of changes

• Build

[qodo-code-review]

Review Summary by Qodo

(Agentic_describe updated until commit 553f0a3)

Bump bazel rules_python to 2.0.1

✨ Enhancement

Walkthroughs

Description

• Bump bazel rules_python from 1.9.0 to 2.0.1
• Updates MODULE.bazel dependency configuration

Diagram

flowchart LR
  A["rules_python 1.9.0"] -- "version upgrade" --> B["rules_python 2.0.1"]
  B -- "MODULE.bazel" --> C["Updated dependency"]

Loading

File Changes

1. MODULE.bazel Dependencies +1/-1

Upgrade rules_python dependency version

• Updated rules_python bazel dependency from version 1.9.0 to 2.0.1
• No other dependencies modified

MODULE.bazel

---

[cgoldberg]

ugh... upgrading to rules_python 2.0.0 breaks the build.

I documented this at: #17404
This needs to be fixed before we can merge this.

[qodo-code-review]

Persistent review updated to latest commit 553f0a3

[qodo-code-review]

Persistent review updated to latest commit 5c5a924

[qodo-code-review]

Persistent review updated to latest commit d044864

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0)

1. Version intent mismatch 🐞 Bug ⚙ Maintainability

Description

MODULE.bazel pins rules_python to 2.0.1, but the PR description states this bump is to 2.0.0; this
inconsistency can mislead reviewers and complicate future dependency-bisects/audits.

Code

MODULE.bazel[40]

+bazel_dep(name = "rules_python", version = "2.0.1")

Evidence

The repo pins rules_python to 2.0.1 in MODULE.bazel, which conflicts with the PR description’s
stated target version (2.0.0).

MODULE.bazel[40-40]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The PR description says the bump is to `rules_python` **2.0.0**, but `MODULE.bazel` pins **2.0.1**. This mismatch is a documentation/intent inconsistency that can cause confusion later.

### Issue Context
`MODULE.bazel` is the source of truth for the module version actually used by Bazel.

### Fix Focus Areas
- MODULE.bazel[40-40]

### Expected fix
Either:
1) Update the PR title/description to say `2.0.1` (if that’s intended), **or**
2) Change `MODULE.bazel` to `version = "2.0.0"` (if 2.0.0 is the intended target).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Previous review results

Review updated until commit 79b8055

Results up to commit 553f0a3

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Version intent mismatch 🐞 Bug ⚙ Maintainability

Description

MODULE.bazel pins rules_python to 2.0.1, but the PR description states this bump is to 2.0.0; this
inconsistency can mislead reviewers and complicate future dependency-bisects/audits.

Code

MODULE.bazel[40]

+bazel_dep(name = "rules_python", version = "2.0.1")

Evidence

The repo pins rules_python to 2.0.1 in MODULE.bazel, which conflicts with the PR description’s
stated target version (2.0.0).

MODULE.bazel[40-40]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The PR description says the bump is to `rules_python` **2.0.0**, but `MODULE.bazel` pins **2.0.1**. This mismatch is a documentation/intent inconsistency that can cause confusion later.

### Issue Context
`MODULE.bazel` is the source of truth for the module version actually used by Bazel.

### Fix Focus Areas
- MODULE.bazel[40-40]

### Expected fix
Either:
1) Update the PR title/description to say `2.0.1` (if that’s intended), **or**
2) Change `MODULE.bazel` to `version = "2.0.0"` (if 2.0.0 is the intended target).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[cgoldberg]

superseded by #17502