Add script for testing uv against different registries

[jtfmumm]

This PR provides a script that uses environment variables to determine which registries to test. This script is being used to run automated registry tests in CI for AWS, Azure, GCP, Artifactory, GitLab, Cloudsmith, and Gemfury.

You must configure the following required env vars for each registry:

    UV_TEST_<registry_name>_URL            URL for the registry
    UV_TEST_<registry_name>_TOKEN       authentication token
    UV_TEST_<registry_name>_PKG          private package to install

The username defaults to "__token__" but can be optionally set with:

    UV_TEST_<registry_name>_USERNAME

For each configured registry, the test will attempt to install the specified package. Some registries can fall back to PyPI internally, so it's important to choose a package that only exists in the registry you are testing.

Currently, a successful test means that it finds the line “ + <package_name>” in the output. This is because in its current form we don’t know ahead of time what package it is and hence what the exact expected output would be. The advantage if that anyone can run this locally, though they would have to have access to the registries they want to test.

You can also use the --use-op command line argument to derive these test env vars from a 1Password vault (default is "RegistryTests" but can be configured with --op-vault). It will look at all items in the vault with names following the pattern UV_TEST_<registry_name> and will derive the env vars as follows:

    `UV_TEST_<registry_name>_USERNAME` from the `username` field
    `UV_TEST_<registry_name>_TOKEN` from the `password` field
    `UV_TEST_<registry_name>_URL` from a field with the label `url`
    `UV_TEST_<registry_name>_PKG` from a field with the label `pkg`

[konstin]

Can we define a default list or target that checks that the tests ran against all known registries?

[jtfmumm]

Can we define a default list or target that checks that the tests ran against all known registries?

Yeah, that’s a good idea.

[jtfmumm]

I've added a cli arg --all that causes the script to check if you've tested known registries. Right now the list is artifactory, azure, aws, cloudsmith, gcp, gemfury, gitlab, and nexus. Even if you don't have credentials for all of them when you run the test, it's helpful as a reminder of other registries to test.

[codspeed-hq]

CodSpeed Walltime Performance Report

Merging #13615 will not alter performance

_{Comparing jtfm/registry-test-script (bcc0f17) with main (49b4501)}

Summary

✅ 12 untouched benchmarks

[jtfmumm]

I've added support for deriving registry env vars from the 1Password cli tool (op) if you pass in the --use-op flag. These values are derived from a specified vault (default is "RegistryTests" but can be configured with --op-vault). It will look at all items in the vault with names following the pattern UV_TEST_<registry_name> and will derive the env vars as follows:

    `UV_TEST_<registry_name>_USERNAME` from the `username` field
    `UV_TEST_<registry_name>_TOKEN` from the `password` field
    `UV_TEST_<registry_name>_URL` from a field with the label `url`
    `UV_TEST_<registry_name>_PKG` from a field with the label `pkg`

If there is no corresponding field for any of these and an env var has been set in the environment, then that will be used.

[jtfmumm]

I've added a CI integration test that runs the registry test script using GitHub secrets to set the env vars. It is currently running against AWS, Azure, GCP, GitLab, Artifactory, Cloudsmith, and Gemfury.