Backport of build: ensure we pull through the hashicorp proxy instead of going directly to the docker hub into release/1.16.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #19482 to be assessed for backporting due to the inclusion of the label backport/1.16.

The below text is copied from the body of the original PR.

---

Description

This should remove the following reason integration tests can flake:

#3 [internal] load metadata for docker.io/hashicorp/consul:latest
#3 ERROR: pulling from host registry-1.docker.io failed with status code [manifests latest]: 429 Too Many Requests
------
 > [internal] load metadata for docker.io/hashicorp/consul:latest:
------
Consul-Dev.dockerfile:5
--------------------
   3 |     
   4 |     ARG CONSUL_IMAGE_VERSION=latest
   5 | >>> FROM hashicorp/consul:${CONSUL_IMAGE_VERSION}
   6 |     RUN apk update && apk add iptables
   7 |     COPY consul /bin/consul
--------------------
ERROR: failed to solve: hashicorp/consul:latest: pulling from host registry-1.docker.io failed with status code [manifests latest]: 4[29](https://github.com/hashicorp/consul/actions/runs/6735998317/job/18310522716?pr=19046#step:7:30) Too Many Requests
Error: Process completed with exit code 1.

---

Overview of commits

• 5ab1e98

[github-team-consul-core-pr-approver]

Auto approved Consul Bot automated PR