Investigate flaky `known_issues/test-vm-timeout-escape-queuemicrotask`

[joyeecheung]

Refs: nodejs/reliability#20

Reason	known_issues/test-vm-timeout-escape-queuemicrotask
Type	JS_TEST_FAILURE
Failed PR	25 (#25441, #24951, #25463, #22712, #25466, #25480, #25430, #25488, #25415, #25479, #25364, #25412, #25472, #25490, #25443, #25502, #25481, #25381, #25429, #25008, #24819, #25507, #25508, #25473, #25455)
Appeared	test-packetnet-centos7-arm64-1, test-packetnet-ubuntu1604-arm64-2, test-packetnet-ubuntu1604-arm64-1, test-joyent-smartos17-x64-2
First CI	https://ci.nodejs.org/job/node-test-pull-request/20074/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/20137/

Example

not ok 2345 known_issues/test-vm-timeout-escape-queuemicrotask
 ---
 duration_ms: 0.333
 severity: fail
 stack: |-
 (node:38468) ExperimentalWarning: queueMicrotask() is experimental.
 ...

[gireeshpunathil]

#25503 might have solved this?

[joyeecheung]

@gireeshpunathil The last failure appeared in https://ci.nodejs.org/job/node-test-pull-request/20137/ so looks like it's been fixed but I'd suggest we observe for a couple days before closing this.

[joyeecheung]

This showed up in 3 out of 58 recent CI runs: nodejs/reliability#21

[gireeshpunathil]

seen again in arm: https://ci.nodejs.org/job/node-test-binary-arm-12+/RUN_SUBSET=0,label=pi2-docker/4569/console

[gireeshpunathil]

and in:

• https://ci.nodejs.org/job/node-test-binary-arm-12+/RUN_SUBSET=0,label=pi2-docker/4568/console
• https://ci.nodejs.org/job/node-test-binary-arm-12+/RUN_SUBSET=0,label=pi2-docker/4567/console
• https://ci.nodejs.org/job/node-test-binary-arm-12+/RUN_SUBSET=0,label=pi2-docker/4566/console
  ...
• https://ci.nodejs.org/job/node-test-binary-arm-12+/RUN_SUBSET=0,label=pi2-docker/4544/console

[Trott]

Hopefully fixed (or at least fixed-ish) by 468bfd3