[Workflow] Restore uv 0.12.9 lockfile generation

[StafaH]

Description

Regenerate uv.lock with uv 0.12.9, restoring the lockfile serialization introduced by #7492 after a later commit accidentally regenerated it with an older uv release.

The refresh also synchronizes the locked versions of nine workspace packages with their current package metadata. No dependency manifests or source files change.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Release backport

• Backport this pull request to the active release branch after it merges into develop

Screenshots

Not applicable.

Validation

• uvx --from uv==0.12.9 uv --version reported uv 0.12.9.
• uvx --from uv==0.12.9 uv lock was idempotent (the lockfile SHA-256 remained unchanged).
• uvx --from uv==0.12.9 uv lock --check passed.
• git diff --check upstream/develop...HEAD passed.
• uvx --from uv==0.12.9 uv run isaaclab -f passed all formatting, syntax, metadata, spelling, and Git LFS hooks except the changelog-fragment hook. That hook compares against a stale local fork base and reports pre-existing package changes and fragment issues; this PR changes no source/ path.

Checklist

• I have read and understood the contribution guidelines.
• I have run the pre-commit checks; the unrelated changelog validation failure is documented above.
• Documentation changes are not required for this lockfile regeneration.
• My changes generate no new warnings.
• No test was added; exact-version lock regeneration, idempotence, and uv lock --check cover this workflow-only fix.
• No changelog fragment is required because no release-managed package under source/ changes.
• My name already exists in CONTRIBUTORS.md.

[isaaclab-review-bot]

Isaac Lab Review Bot

Reviewed the lockfile-only regeneration intended to restore uv 0.12.9 serialization and synchronize workspace package metadata. No manifests, source files, or documentation are changed, and no actionable issue is established by the supplied review evidence.

• Design and architecture: The change is confined to the generated uv.lock artifact, so module boundaries, dependency direction, and extension lifecycle behavior are unaffected. Regenerating with the intended uv release is consistent with the stated workflow correction.
• API: No public Python APIs, exports, CLI arguments, configuration surfaces, or documentation integrations are changed. Because no release-managed source package changes, the changelog-fragment requirement is not implicated.
• Implementation: The reported uv 0.12.9 idempotence and uv lock --check validations are appropriate for a lockfile regeneration. The lockfile diff was not included in the supplied context, so the serialization and nine workspace-version updates could not be independently inspected; this is a review limitation rather than a demonstrated defect.

No blocking issues. No inline issue met the actionable-evidence threshold; the assessment above records the review feedback.

Automated review; human maintainers own approval decisions.

[StafaH]

run-ci