Fix uv all-extras dependency resolution

[ParamThakkar123]

Motivation

• Avoid an unsatisfiable install when requesting torchwm[all] caused by mlagents-envs pulling incompatible NumPy ranges.
• Ensure optional extras do not force versions that conflict with the lockfile artifacts or the project NumPy requirement.
• Allow uv to parse and use the existing lockfile by fixing mismatched package version headers that prevented lock parsing.

Description

• Constrain the ml-agents extra in pyproject.toml to mlagents-envs>=0.28.0,<0.29.0 to keep it compatible with the project numpy>=1.26.0 requirement.
• Lowered several optional dependency minima in pyproject.toml: python-multipart -> >=0.0.22, starlette -> >=0.52.1, gitpython -> >=3.1.46, and mistune -> >=3.2.0 so they match the versions represented in the lockfile.
• Updated uv.lock package version headers and related metadata to match artifact filenames (notably gitpython, idna, mistune, pillow, python-dotenv, python-multipart, starlette, urllib3) and updated the ml-agents metadata specifier to >=0.28.0,<0.29.0 so the lockfile parses cleanly and is consistent with the declared constraints.

Testing

• Ran a TOML/lockfile validation script (python - <<'PY' ... PY) that verified pyproject.toml and uv.lock parse and that lockfile package versions match artifact filenames (passed).
• Ran git diff --check to confirm no whitespace/conflict markers (passed).
• Attempted uv sync --all-extras --locked --dry-run and uv sync --all-extras --locked --dry-run --no-build-isolation; both progressed past lock parsing but ultimately failed in this environment due to network/tunnel errors and a missing local setuptools respectively (environmental failures, not changeset regressions).

---

Codex Task