test uv publish fails with expired GitLab PAT #1950

Run: https://github.com/astral-sh/uv/actions/runs/35292260042
Job: https://github.com/astral-sh/uv/actions/runs/35292260042/job/105438658319

The CI workflow failed on a push to main, attempt 1, in the test uv publish job on Ubuntu 24.04 x86_64. The only failed step was Publish test packages:

error: Failed to publish the wheel to the GitLab package registry
  cause: Server returned status code 401 Unauthorized. Server says: {"error":"invalid_token","error_description":"Token is expired. You can either do re-authorization or token refresh."}

The workflow supplies a dedicated GitLab publishing PAT to scripts/publish/test_publish.py, and the script uses it as the password for the GitLab target. GitLab's response directly establishes that this credential has expired, so it must be reauthorized, refreshed, or rotated. Expiration monitoring or a rotation procedure would help prevent the same default-branch outage.

The triggering change came from astral-sh#21810 and modified only crates/uv-once-map/src/lib.rs, making it unrelated to the publishing credential. This was the run's only independent failure.

#758 and #759 track 401 responses from the separate registry integration job using a different configured credential. #752 tracks an earlier GitLab pipeline-trigger failure in this job, not package-upload authentication.