fix: crash on WebWorker destruction

[codebytere]

Description of Change

Closes #35384.
Closes #35442.

Fixes a potential crash on WebWorker destruction. This was happening as a result of our custom UV_LOOP_INTERRUPT_ON_IO_CHANGE code added to libuv, as uv_loop_close results in a call to uv__io_stop, which then calls uv__loop_interrupt. uv__loop_interrupt didn't account for the case where the loop was no longer alive, and so would crash. This fixes that.

This PR also switches over from a direct call to uv_loop_close to Node's wrapper CheckedUvLoopClose, which calls uv_loop_close as expected but also aids in future debugging by logging all open handles should they exist.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Fixed a potential crash on WebWorker destruction.

[deepak1556]

uv__loop_interrupt didn't account for the case where the loop was no longer alive, and so would nullptr crash. This fixes that.

@codebytere which call ends up with nullptr ? The fix in this PR seems to more likely avoid the abort call instead if I am not mistaken.

[zcbenz]

It seems that it is abort crash instead of nullptr crash.

From the crash report:

Crashed Thread:        20  DedicatedWorker thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called

[codebytere]

That's correct. It is an abort crash, i miswrote it.

[codebytere]

#
# Fatal error in ..\..\v8\src\builtins\profile-data-reader.cc, line 52
# Check failed: Can't read log file.
#
#

is a known flake cc @VerteDinde

[release-clerk]

Release Notes Persisted

Fixed a potential crash on WebWorker destruction.

[trop]

I have automatically backported this PR to "19-x-y", please check out #35490

[trop]

I have automatically backported this PR to "20-x-y", please check out #35491

[trop]

I have automatically backported this PR to "21-x-y", please check out #35492