zarf's message when you hit the pull rate limit isn't helpful

[bdw617]

my PC (main, 0.30.1+)

Steps to reproduce

1. do not be logged into docker.io
2. run make test-e2e too often

workaround is to simply login to docker.io. but still we shouldn't use it as part of our constantly run testing as much.

Expected result

it should run successfully.

Actual Result

➜ zarf git:(main) ✗ docker pull docker.io/defenseunicorns/zarf-game:multi-tile-dark
Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

Visual Proof (screenshots, videos, text, etc)

  ⠋  Falling back to docker for docker.io/defenseunicorns/zarf-game:multi-tile-dark. This may take some time.
  ⠋  Falling back to docker for docker.io/defenseunicorns/zarf-game:multi-tile-dark. This may take some time.
  ⠋  Falling back to docker for docker.io/defenseunicorns/zarf-game:multi-tile-dark. This may take some time.
     ERROR:  Failed to create package: unable to pull images after 3 attempts: failed to load metadata for all
             images. This may be due to a network error or an invalid image reference: failed to pull image
             docker.io/defenseunicorns/zarf-game:multi-tile-dark: failed to inspect image
             docker.io/defenseunicorns/zarf-game:multi-tile-dark via docker: Error response from daemon: No such
             image: defenseunicorns/zarf-game:multi-tile-dark

Severity/Priority

Low

[bdw617]

the CI pipeline got this message today:

 ERROR:  Failed to create package: unable to pull images after 3 attempts: failed to load metadata for all
 images. This may be due to a network error or an invalid image reference: failed to pull image
 public.ecr.aws/docker/library/redis:7.0.11-alpine: failed to pull image
 public.ecr.aws/docker/library/redis:7.0.11-alpine: GET
 https://public.ecr.aws/v2/docker/library/redis/manifests/sha256:ed439ea2fd065ac9622bf40b8bdb156e1e2bb2b73f7877f430775b8d728b3eec:
 TOOMANYREQUESTS: Rate exceeded

[bdw617]

In a zarf message:

|      ERROR:  Failed to create package: unable to pull images after 3 attempts: failed to load metadata for all
|              images. This may be due to a network error or an invalid image reference: failed to pull image
|              docker.io/library/httpd:alpine3.18: failed to inspect image docker.io/library/httpd:alpine3.18 via
|              docker: Error response from daemon: No such image: httpd:alpine3.18

if you run docker pull directly:

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

it appears to be crane that doesn't expose the message from the server on failure, so the message just says nope, it's not there. we should see if there's a way to improve this, maybe a PR against crane.

[bdw617]

I've validated where the problem is and it's fixable within zarf. Crane hides the underlying transport info in the error, but Zarf doesn't print out the error from crane unless you have debug on. It's an actual bug, If it can't pull remotely and fails to pull locally, Zarf pull.go loses the original error unless you have debug on.