fix: Upgrade yapf to v0.40.2 for Python 3.13+ compatibility. Fixes #12393

[Pyfagorass]

Summary

This PR fixes the pre-commit failure on Python 3.13+ by upgrading yapf to v0.40.2, which no longer depends on lib2to3.

Problem

• yapf v0.32.0 (currently in .pre-commit-config.yaml) depends on lib2to3
• lib2to3 was removed from Python 3.13 standard library (deprecated in Python 3.11)
• This causes ModuleNotFoundError: No module named 'lib2to3' when running pre-commit hooks with Python 3.13+

Solution

• Switch from github.com/pre-commit/mirrors-yapf (archived Jan 2023) to github.com/google/yapf (actively maintained)
• Upgrade yapf from v0.32.0 to v0.40.2

Testing

Verified pre-commit hooks work successfully with:

• ✅ Python 3.12.6: All hooks pass
• ✅ Python 3.13.9: All hooks pass (no lib2to3 error)

References

• Issue: [bug] Pre-commit fails due to yapf dependency on lib2to3 in Python 3.12+ #12393
• Python 3.13 What's New: https://docs.python.org/3/whatsnew/3.13.html

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign humairak for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[google-oss-prow]

Hi @Pyfagorass. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.