Determine naming conventions for non-dockerhub container pushes

This is a list of naming conventions we have in the different repositories which we use which can be used as input to what we do in the future, particularly for [an alternate repository for the end-user temurin images](https://github.com/adoptium/containers/issues/843).

While we will likely leave the dockerhub ones as-is, since we are now aiming to push to alternate repositories we should look at the naming conventions in use and select which ones to use for the test-container publishing (Will likely be moved to `adoptium_test_image` instead of `test-containers` on ghcr to avoid confusion and align with the build image naming).

The expectation is that all of the images pushed to locations other than dockerhub will be verifiable using [sigstore](https://github.com/adoptium/infrastructure/issues/2734).

Naming conventions already in use:
- [dockerhub official images](https://hub.docker.com/_/eclipse-temurin/tags):
- `eclipse-temurin:8u472-b08-jdk-ubi9-minimal`, `8-jdk-ubi9-minimal`, `8-jdk`, `8`
- [adoptopenjdk official images](https://hub.docker.com/_/adoptopenjdk/tags)
- Similar to the above - no longer maintained e.g. `adoptopenjdk/8u292-b10-jre-openj9-0.26.0`
- [adoptopenjdk standard](https://hub.docker.com/r/adoptopenjdk/openjdk8) (updated by [openjdk_build_docker_multiarch](https://ci.adoptium.net/job/openjdk_build_docker_multiarch/))
- Separate per version e.g. `adoptopenjdk/openjdk8:aarch64-ubi-jdk8u292-b10-slim` or ` jdk8u292-b10-ubi-slim` or `ubi-slim`
- [build images](https://hub.docker.com/r/adoptopenjdk/centos7_build_image/tags) (under same adoptopenjdk repo as the last one - updated by [centos7_docker_image_updater](https://ci.adoptium.net/job/centos7_docker_image_updater/))
- `adoptopenjdk/centos7_build_image:linux-amd64` or just `adoptopenjdk/centos7_build_image`
- [GHCR test-containers](https://github.com/orgs/adoptium/packages/container/test-containers/versions?filters%5Bversion_type%5D=tagged) (Updated by [test_image_updater](https://ci.adoptium.net/job/test_image_updater/)
- `ghcr.io/adoptium/test-containers:ubi10-arm64` or `ghcr.io/adoptium/test-containers:ubi10`
- [GHCR build images](https://github.com/orgs/adoptium/packages/container/package/adoptium_build_image) - updated by [build_image_updater](https://ci.adoptium.net/job/build_image_updater/))
- `ghcr.io/adoptium/adoptium_build_image:centos7_linux-arm64` or `centos7`

Start by reviewing the linked Docker Hub and GHCR image examples, the test_image_updater and build_image_updater jobs, and the related issues #843 and infrastructure #2734. Done means selecting documented naming conventions for non-Docker Hub pushes, including the proposed test image name, with the sigstore verification expectation accounted for.

Written by the indexing model from the issue text.