Add e2e test for authorized pull/push to private repo

[AryanSharma9917]

- What I did

Added an end-to-end (e2e) test to verify authenticated pull and push operations to a private Docker registry.

- How I did it

Created e2e/auth_test.go which:

• Uses environment variables for credentials (DOCKER_USERNAME, DOCKER_PASSWORD, PRIVATE_REPO)
• Logs in to Docker registry
• Pulls, tags, pushes, removes, and pulls back a Docker image

- How to verify it

Run the e2e test with the required environment variables set in your local or CI environment.

- Human readable description for the release notes

Add e2e test for authenticated pull/push to private Docker registry

- Related issue
Closes #5965

[vvoland]

Thanks!

This should setup a temporary registry with auth that the CLI connects to, so we don't rely on the Docker Hub and don't need to put real credentials for tests.

[AryanSharma9917]

Thanks!

This should setup a temporary registry with auth that the CLI connects to, so we don't rely on the Docker Hub and don't need to put real credentials for tests.

Thanks! I’ll update the test to spin up a temporary registry:2 container with htpasswd-based auth and run push/pull operations against it locally.

[AryanSharma9917]

@vvoland could you please give my PR review?

[vvoland]

Hi, looks like the CI is red