Bump rules_python to 2.2.0

[dzbarsky]

Summary

Bump rules_python from 1.7.0 to 2.2.0 and regenerate MODULE.bazel.lock with Bazel 9.1.1.

This gives us bazel-contrib/rules_python@1d99f70 which closes a hermiticity gap experienced by Bazel's own build.

Build API Changes

No.

Validation

Release Notes

RELNOTES: None

[gregestren]

Is the failing CI okay?

[dzbarsky]

Is the failing CI okay?

I think so? I have seen various windows shard failures on many PRs recently. This one is:

ERROR: C:/b/6s3poxhi/execroot/_main/_tmp/4d39d5a325ce8c71aa2ebb418c2fd310/_bazel_b/hu7r7lhl/external/bazel_tools/src/main/cpp/util/BUILD:96:11: Compiling src/main/cpp/util/port.cc failed: absolute path inclusion(s) found in rule '@@bazel_tools//src/main/cpp/util:port':
the source file 'src/main/cpp/util/port.cc' includes the following non-builtin files with absolute paths (if these are builtin files, make sure these paths are in your toolchain):
'C:/Program Files/LLVM/lib/clang/22/include/stddef.h'
'C:/Program Files/LLVM/lib/clang/22/include/__stddef_header_macro.h'
'C:/Program Files/LLVM/lib/clang/22/include/__stddef_ptrdiff_t.h'
'C:/Program Files/LLVM/lib/clang/22/include/__stddef_size_t.h'
'C:/Program Files/LLVM/lib/clang/22/include/__stddef_wchar_t.h'
'C:/Program Files/LLVM/lib/clang/22/include/__stddef_null.h'
'C:/Program Files/LLVM/lib/clang/22/include/__stddef_nullptr_t.h'
'C:/Program Files/LLVM/lib/clang/22/include/__stddef_max_align_t.h'
'C:/Program Files/LLVM/lib/clang/22/include/__stddef_offsetof.h'
'C:/Program Files/LLVM/lib/clang/22/include/yvals_core.h'
'C:/Program Files/LLVM/lib/clang/22/include/vadefs.h'
'C:/Program Files/LLVM/lib/clang/22/include/yvals_core.h'
'C:/Program Files/LLVM/lib/clang/22/include/stdint.h'
'C:/Program Files/LLVM/lib/clang/22/include/inttypes.h'
Target @@bazel_tools//src/tools/launcher:launcher failed to build

Hopefully we can swap to @llvm soon to get a hermetic cc toolchain and put an end to these issues :)

[fmeum]

Yes, this will be fixed by a rules_cc update @pzembrod

[gregestren]

Indeed. Looks like nothing's passing recently. #30114

[iancha1992]

Missing a function docstring here. Could you please add? @dzbarsky

[iancha1992]

@dzbarsky Thank you! We're currently working on merging this.

[gregestren]

Is there any reason not to merge now (aside rfom the branch conflict - can we resolve that?)

[iancha1992]

Is there any reason not to merge now (aside rom the branch conflict - can we resolve that?)

Is there any reason not to merge now (aside rom the branch conflict - can we resolve that?)

@gregestren I was working on merging this. I'll assign you as a reviewer as well along with @aranguyen. Also, the merge conflict you see is from the MODULE.bazel.lock, which we can resolve on our own internally by updating the lockfile. So no need for the PR author to fix this since all other tests passed.