Switch active Python LSP modules from Pyright to ty

[ryantm]

Why

We want all active (non-historical) Python module configurations to use Astral's ty language server instead of Pyright.

What changed

• Added a new active ty module at pkgs/modules/ty/default.nix that exposes replit.dev.languageServers.ty.
• Updated active Python tool modules (python-*) to register ty as their language server instead of pyright-extended.
• Replaced active module imports of pyright and pyright-extended with ty in pkgs/modules/default.nix.
• Added upgrade-map entries so legacy module IDs pyright and pyright-extended resolve to ty.
• Updated python-base module copy to reference the ty module.

[ryantm@replit2:~/replit/nixmodules]$ /nix/store/775cppcslcvxd4x2v8x4k78xw94zg88a-ty-0.0.21/bin/ty --version
ty 0.0.21

Test plan

• nix build '.#activeModules."python-3.11"' '.#activeModules.ty'
• nix eval --raw '.#modules.pyright.outPath'
• nix eval --raw '.#modules."pyright-extended".outPath'
  • Verified both legacy IDs resolve to the same module outPath as ty.
• nix flake check --no-build
  • Evaluates the flake outputs, but still hits the existing repo issue where packages.x86_64-linux.deploymentModules is not a derivation.

Rollout

No special rollout steps required.

• This is fully backward and forward compatible

Revertibility

Safe to revert. This change only updates module wiring and language server configuration (no schema/data migrations or irreversible infra changes).

~ written by Zerg 👾