fix: clear pending TLS socket handle

[christian-bromann]

What kind of change does this PR introduce?

I recognised when calling canDownload the @puppeteer/browsers package makes a HEAD request, e.g. to https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/116.0.5793.0/mac-arm64/chrome-mac-arm64.zip. This causes the Node.js process to stale as there stay pending TLSSocket around

Did you add tests for your changes?

I am currently working on webdriverio/webdriverio#10767 and have been encountered this issue. Adding given code line resolves it.

My current workaround is:

setTimeout(() => {
    for (const handle of process._getActiveHandles()) {
        if (handle.servername && handle.servername.includes('edgedl.me')) {
            handle.destroy()
        }
    }
}, 10)

If relevant, did you update the documentation?

Summary

Does this PR introduce a breaking change?

I don't think so.

Other information

[conventional-commit-lint-gcf]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

[Lightning00Blade]

Thank you for your PR, I left a small comment and after #10668 is merged test should pass as well.

[christian-bromann]

Thanks for the review @Lightning00Blade!

You are totally right, request.resume() is the right thing to call here. Update the PR and PR message, everything should pass now.