Renamed for testing

[hashicorp-vault-sonar-prod]

The latest CI run on master is red: Build (Analysis on Sonarcloud.io, sqc-eu, SonarSource_sonar-python) (run 103195868663).

This PR was opened with an empty commit to reserve a place for the CI fix.

[hashicorp-vault-sonar-prod]

gitar auto-apply:on

[hashicorp-vault-sonar-prod]

gitar master CI is failing: https://github.com/SonarSource/sonar-python/actions/runs/34573757506/job/103195868663

1. Investigate the failure.
2. If it looks transient or flaky, retry it.
3. If it's a real issue, fix it in this PR.
4. If you can't fix it, leave a comment explaining your investigation.
5. If there's nothing to fix, reply with "This PR can be closed now" and your investigation notes.

[gitar-bot]

Investigated the failure at https://github.com/SonarSource/sonar-python/actions/runs/34573757506/job/103195868663.

Root cause: the python-frontend module's exec-maven-plugin:exec (serializer-runner) goal invokes uv run python -m pytest tests/ for the typeshed serializer. uv failed to resolve/download a dependency (tornado==6.3.1) from the internal Artifactory PyPI mirror (repox.jfrog.io), receiving an HTTP 401 Unauthorized.

This is not a code issue in this PR — the PR itself contains no file changes. It's an authentication/infrastructure problem with the internal sonarsource-pypi Artifactory proxy. Checking other recent master Build failures (e.g. runs 34553018130, 34378136500) shows the same pattern: different packages (pydantic==1.10.26, etc.) failing with the identical 401 error from the same Artifactory endpoint, confirming this is a recurring credential/infra issue rather than something specific to this commit or a one-off flake.

Since there's no code fix available for an Artifactory authentication problem, and it recurs across unrelated commits, I can't resolve this from within the repo. This needs infra/credentials attention on the Artifactory PyPI proxy (repox.jfrog.io/artifactory/api/pypi/sonarsource-pypi) side.

This PR can be closed now.