Test Replay: [Upload] Update timeout logic to fail faster on catastrophic timeouts about cypress HOT 1 CLOSED

I think we can simplify this a little - copying what @cypress/request does may not be the best course.

cypress/request connection timeouts have a maximum of the OS-wide TCP connection timeout. Increasing this won't have any effect, and reducing this would probably only cause a higher error rate. I'd prefer to keep this at the OS-specified value; extending @packages/network Agent will be expensive to implement, and likely won't have a high rate of return.

Status code available sent is only important in error cases I think, which will simply reject the promise.

Data flowing is a great metric for timing out an upload, because it's what's important to the success of the upload.

I suggest:

• Timeout on "Upload Begin": the interval between fetch being called and the first .write to an intermediate .pipe from the artifact's ReadableStream. This handles: socket connect, http status/headers available (if sent prior to upload beginning). This is to detect initial connection errors.
• Timeout on "Upload Progress": the time between each .write to an intermediate .pipe from the artifact's ReadableStream. This is to detect stalled uploads.
• No timeout on upload complete: the upload duration is too variable to choose a good number, and the error case (a stalled upload) is already handled by the progress timeout.

What do you think?

from cypress.