Context

Describe the background behind the problem.

PYTHON-5956 introduces a shared uv+just setup action in mongodb-labs/drivers-github-tools, replacing duplicated CI setup steps in mongo-python-driver. Other Python team repos maintain the same kind of duplicated uv/just setup in their own CI workflows and should migrate to the shared action once it's available. Consider doing this in lockstep with PYTHON-5922, which adds just support across repos.

Track rollout progress in the tracking sheet: https://docs.google.com/spreadsheets/d/1hPPTY6ifDCDocYGzqkbJfr3_tAcj70IiBh7yb6SEBBo/edit?gid=0#gid=0

Definition of done

What must be done to consider the task complete?

Each Python team repo using uv/just in CI has adopted the shared setup action in place of its own duplicated steps, with no change in CI behavior or coverage. The tracking sheet reflects the final status for every repo.

Pitfalls

What should the implementer watch out for? What are the risks?

• Repos may have setup steps that diverge slightly from PyMongo's (different inputs, skipped steps, etc.), so migrations aren't guaranteed to be identical copy-paste.
• Some repos may not need the dependency-install behavior and should opt out rather than have it forced on.
• Coordinate timing with each repo's own release/CI schedule to avoid disruptive changes.