Debugger `paused` event is sometimes not delivered to inspector client on macOS CI

We have multiple macOS CI debugger flakes where the debuggee appears to pause, but the
inspector client process never observes the expected Debugger.paused event.

This has affected interactive debugger tests and probe mode. In probe mode, handlePaused()
should either record hits or resume unknown pauses. When the report has no hits and eventually
times out, the most likely signal is that the paused event never reached the inspector client
process.

The AI-assisted PRs have mostly tried to address nearby symptoms or test races, but they have
not resolved the underlying observation:

• #63608 deferred probe pause handling until startup completed.
• #63632 changed exception-pause behavior.
• #63944 adjusted a probe fixture to avoid missed startup breakpoints.
• #63968 changed tests to wait for paused state instead of pause-banner output.

Refs: https://github.com/nodejs/node/pull/63632#issuecomment-4583515968

The question we need to answer is

Why is Debugger.paused sometimes never delivered to the inspector client process on macOS CI?

Empieza reproduciendo los fallos intermitentes del depurador en macOS CI y rastreando la entrega entre el debuggee, el proceso cliente del inspector y handlePaused() en modo probe. Lee los intentos anteriores en #63608, #63632, #63944 y #63968, especialmente la discusión de #63632 a la que se hace referencia. Se considera terminado cuando se haya identificado la causa del evento Debugger.paused ausente y los casos afectados del depurador interactivo y del modo probe ya no agoten el tiempo de espera.