chore: refresh pixi lockfiles

[github-actions]

Automated lockfile refresh using pixi v0.73.0 (pixi update --no-install, followed by byte-stable pixi lock --check canonicalization for each refreshed workspace).

Note

cuda_core/pixi.lock was left unchanged because Pixi v0.73.0 reproduced the exact known samples-source pruning defect. Other workspaces were refreshed normally.

Lockfiles covered by the refresh:

• pixi.lock
• benchmarks/cuda_bindings/pixi.lock
• benchmarks/cuda_core/pixi.lock
• cuda_bindings/pixi.lock
• cuda_core/pixi.lock
• cuda_pathfinder/pixi.lock

See #2298 and #2849.

Important

This PR was opened with GITHUB_TOKEN. A maintainer with write access must:

1. Select Approve workflows to run in the merge box.
2. Assign themselves to this PR. The human-generated assigned event
   creates the required PR has assignee, labels, and milestone check
   and gives the PR a clear owner.

If the diff looks wrong, close this PR and leave the branch deleted; the
next scheduled run opens a fresh one if an update is still needed.

[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.

[rwgk]

Closing: We should deliberately pause Pixi freshness enforcement until the upstream bugs are fixed. See my comments under #3065.