TestInfra_runEnvoy_stopEnvoy failing

*Description*:
>What issue is being seen? Describe what should be happening instead of
the bug, for example: The expected value isn't returned, etc.

```
looking up the latest Envoy version
downloading https://archive.tetratelabs.io/envoy/download/v1.36.2/envoy-v1.36.2-linux-amd64.tar.xz
--- FAIL: TestInfra_runEnvoy_stopEnvoy (25.11s)
proxy_infra_test.go:102:
Error Trace: /home/runner/work/gateway/gateway/internal/infrastructure/host/proxy_infra_test.go:102
Error: Received unexpected error:
error untarring https://archive.tetratelabs.io/envoy/download/v1.36.2/envoy-v1.36.2-linux-amd64.tar.xz: read tcp 10.1.0.186:43232->185.199.110.133:443: read: connection reset by peer
Test: TestInfra_runEnvoy_stopEnvoy
looking up the latest Envoy version
downloading https://archive.tetratelabs.io/envoy/download/v1.36.2/envoy-v1.36.2-linux-amd64.tar.xz
starting: /tmp/TestInfra_runEnvoy_OutputRedirection2933253686/001/versions/1.36.2/bin/envoy with logs in /tmp/TestInfra_runEnvoy_OutputRedirection2933253686/001/runs/1761269928025223172

/tmp/TestInfra_runEnvoy_OutputRedirection2933253686/001/versions/1.36.2/bin/envoy version: dc2d3098ae5641555f15c71d5bb5ce0060a8015c/1.36.2/Clean/RELEASE/BoringSSL
```

*Repro steps*:
> Include sample requests, environment, etc. All data and inputs
required to reproduce the bug.

>**Note**: If there are privacy concerns, sanitize the data prior to
sharing.

*Environment*:
>Include the environment like gateway version, envoy version and so on.

*Logs*:
>Include the access logs and the Envoy logs.