Migration needed for Automatic Exec Groups

Migration to [Automatic Exec Groups](https://bazel.build/extending/auto-exec-groups) (AEGs) is needed since its incompatible flag (--incompatible_auto_exec_groups) will be enabled for Bazel@Head by default next week (week of 14th of October), thus it will be breaking [rules_python](https://github.com/bazelbuild/rules_python). Please migrate and fix potential errors, in order to unblock your project and users who depend on your project. Potential errors can be triggered by building your project with this incompatible flag. Note that AEGs will not be flipped by default for Bazel 8, but for Bazel at head after Bazel 8 cut.

For more details, please check:
- [The reference issue ](https://github.com/bazelbuild/bazel/issues/19981)
- [General Bazel documentation for AEGs](https://bazel.build/extending/auto-exec-groups)
- Particularly interesting parts could be
- [Most common errors](https://bazel.build/extending/auto-exec-groups#potential-problems) you could see during this migration
- [How to disable AEGs](https://bazel.build/extending/auto-exec-groups#how-disable) until fully migrated

Never heard of incompatible flags before? We have [documentation](https://docs.bazel.build/versions/master/backward-compatibility.html) that explains everything.

If you have any questions, please file an issue in https://github.com/bazelbuild/bazel/issues.

Read the linked Bazel Automatic Exec Groups documentation and reference issue first. Build rules_python with --incompatible_auto_exec_groups enabled, investigate the resulting errors, and migrate the affected rules so the project builds successfully with the flag enabled.

Written by the indexing model from the issue text.