Socket hang up when uploading to server

I've gone down a bit of a rabbit hole trying to figure out why I kept getting a socket timeout error from the electron-forge publisher.

I eventually realized that when I was doing the upload at exactly **2 minutes** the upload was failing with this message:

```
An unhandled error has occurred inside Forge:
request to http://localhost:3030/rest/app/1/channel/eb76a4a94e2a588b9cb9302826aa796f/upload failed, reason: socket hang up
FetchError: request to http://localhost:3030/rest/app/1/channel/eb76a4a94e2a588b9cb9302826aa796f/upload failed, reason: socket hang up
at ClientRequest. (D:\GitHub\brl-desktop-app\node_modules\node-fetch\dist\index.js:3190:14)
at ClientRequest.emit (events.js:310:20)
at ClientRequest.EventEmitter.emit (domain.js:482:12)
at Socket.socketOnEnd (_http_client.js:453:9)
at Socket.emit (events.js:322:22)
at Socket.EventEmitter.emit (domain.js:482:12)
at endReadableNT (_stream_readable.js:1187:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
```

I was simulating a prod server in a local docker compose file but connecting to an actual S3 bucket to test out aspects of the prod infrastructure.

Start by reproducing the electron-forge publisher upload with the local Docker Compose server and the actual S3 bucket, focusing on the failure at exactly two minutes. Trace the /rest/app/1/channel/.../upload request and its socket timeout; done means the upload no longer hangs and the behavior is covered by a verified test or reproduction.

Written by the indexing model from the issue text.