Increased errors for Package Registry

Users may see 403 or 402 errors when pushing python packages to the registry using `CI_JOB_TOKEN`. We are aware of the issue and a fix is in the works.

As a workaround, affected users can use a Personal or Project Access Token to authenticate.

See here for more details: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19436

The fix is understood but is still in progress. See here for details: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19436

No significant updates at this time. Please see here for details: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19436

The fix has been deployed and we are monitoring the situation. Please see here for more information: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19436

The fix has been deployed, and this incident is now considered resolved. Please open a support ticket if you still have issues using `CI_JOB_TOKEN`. See this issue for more details: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19436

We are still observing issues and are investigating a fix.

Please open a support ticket if you still have issues using `CI_JOB_TOKEN`. See this issue for more details: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19436

No substantial updates at this time.

Please open a support ticket if you still have issues using `CI_JOB_TOKEN`. See this issue for more details: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19436

No further significant updates at this time.

Please see here for details: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19436

The fix has been identified and we are now awaiting the deployment. We will update once the deployment has completed.

Please open a support ticket if you still have issues using `CI_JOB_TOKEN`. See this issue for more details: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19436