chore: pin pip for good.

[pwnage101]

Lets stop beating around the bush. edx-lint has added and removed this exact pin four times:

• 2026-02-11 8578cb5 chore: Unpin pip < 26.0
• 2026-02-03 e930f47 fix: pin pip < 26.0
• 2025-12-05 dcb92c5 fix: remove pip-tools common_constraint
• 2025-10-29 4410a03 fix: pin pip<25.3 to resolve make upgrade build failure
• 2025-10-01 136df76 fix: Drop the constraint on pip
• 2024-10-28 bf7ca95 chore: add common constraint for pip (pip<24.3)
• 2022-05-16 fdddf3b fix: remove pip common constraint

Until we finally migrate off pip-tools entirely, realistically we need to keep a permanent pip constraint in common_constraints.txt.

[Copilot]

Pull request overview

Adds a semi-permanent pip upper-bound to common_constraints.txt to prevent pip upgrades from breaking pip-tools consumers, with detailed rationale and explicit removal criteria.

Changes:

• Introduces a documented, semi-permanent pip<26.2 constraint in common_constraints.txt.
• Adds guidance on when/how to bump or remove the constraint (e.g., after pip-tools releases, or after migrating away from pip-tools).

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[bmtcril]

Seems reasonable while we do the migration. Since the issue that prompted this is fixed in pip-tools 7.6.1, can you just bump the pin to the latest 26.2.1?