ci - `Initialize containers` fails intermittently

### What is this about?

```
read tcp 10.1.0.86:60262->185.199.108.154:443: read: connection reset by peer
Error: Docker pull failed with exit code 1
```

Example: https://github.com/MetaMask/metamask-extension/actions/runs/17908262023/job/50914430371

### Scenario

_No response_

### Design

_No response_

### Technical Details

_No response_

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

_No response_

Start with the linked GitHub Actions run and inspect the `Initialize containers` step and its Docker pull configuration. Determine why the pull intermittently receives a connection reset, then verify that the workflow completes successfully without this failure.

Written by the indexing model from the issue text.