chore(beep boop 🤖): Bump uv.lock (main, mcore-dev) (2026-06-09)

[svcnvidia-nemo-ci]

🚀 PR to bump uv.lock in main.

🤖 This PR will be merged automatically once CI passes.

[svcnvidia-nemo-ci]

/ok to test a2fb291

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[yaoyu-33]

MCore bump auto-fix status for dev:

Classification: MCore broke Bridge
Evidence: main / mcore-dev PR #4232 still fails on 2026-06-09. CICD NeMo run 27200431963, job Launch_Unit_Tests_Core 80317406108, fails during unit-test collection at 2026-06-09 12:04 UTC because src/megatron/bridge/utils/common_utils.py:25 imports safe_get_world_size from megatron.core._rank_utils; Installation Test job 80302805211 and release build job 80302863418 fail on the same import. MCore compare 6204b925f3da8b998524c6bb47a9ca779d95ce2e...39f8d5524d2de6f14292eb4945a6b0ba9b06f29f shows the old _rank_utils.py had safe_get_world_size() and the new target no longer defines it.
Fix PR: #4094. I did not open a duplicate fix PR because #4094 already covers this target failure with Bridge-owned rank/world-size helpers and has open review state.
Guards: none added by this worker; #4094 uses Bridge-owned helper code rather than adding a new MCore commit guard.
Validation: no new branch or CW interactive validation was run by this worker because the failure is already covered by #4094. Existing #4094 validation from 2026-05-31 shows Installation Test, CICD NeMo, release build, unit tests, and L0/L1/L2 jobs passing; current blocker is codecov/patch plus review/merge state.
Next action: review and merge #4094, then rerun or wait for the next main / mcore-dev automated bump to confirm #4232's import-time failure is cleared.