Fix Artifact Registry setup authentication

What does this MR do and why?

This MR updates Artifact Registry setup snippets to use exchanged Artifact Registry tokens with Basic authentication.

The snippets cover Maven, Gradle, npm, Yarn, Docker, Podman, and sbt. This MR adds sbt to the Maven build-tool choices. It configures the sbt resolver for install and publishTo for publish. Docker and Podman preserve non-default registry ports.

Changelog: fixed EE: true

References

gitlab-org/ops/artifact-registry#1039 (closed)

Screenshots or screen recordings

No screenshots are provided. The snippets change only after the user selects a tool.

How to set up and validate locally

Run:

node_modules/.bin/jest --config jest.config.js --runInBand ee/spec/frontend/packages_and_registries/artifact_registry/repositories/detail/setup_instructions/snippets_spec.js ee/spec/frontend/packages_and_registries/artifact_registry/repositories/detail/setup_instructions/setup_snippets_spec.js ee/spec/frontend/packages_and_registries/artifact_registry/repositories/detail/artifacts_empty_state_spec.js ee/spec/frontend/packages_and_registries/artifact_registry/repositories/detail/setup_instructions/tool_selector_spec.js ee/spec/frontend/packages_and_registries/artifact_registry/repositories/versions/detail/version_overview_spec.js

The five Artifact Registry frontend specs passed with 307 tests.

Pre-push checks passed:

• Prettier
• ESLint
• Dependency rules
• Gettext
• Secrets detection
• Security harness

MR acceptance checklist

• The setup snippets use exchanged Artifact Registry tokens.
• The setup snippets use Basic authentication.
• The affected frontend specs pass.