test: re-enable Node.js tests that now pass with BoringSSL - #55096

* test: re-enable Node.js tests that now pass with BoringSSL

Most of these were disabled because BoringSSL behaved differently from
OpenSSL. Upstream Node.js made the tests BoringSSL-aware in
nodejs/node#63161 (v24.18.0) and fixed the ML-KEM expectations in
nodejs/node#65966 (v24.22.0), so they now pass.

The es-module/test-esm-wasm entry is a stale prefix: test.py matches
entries as substrings of the path, so it was hiding 13 split files that
pass. A few entries are dropped because the tests now skip themselves.

parallel/test-cluster-primary-error, parallel/test-cluster-primary-kill,
parallel/test-diagnostics-channel-memory-leak and
parallel/test-worker-resource-limits move to the flaky list instead.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CfxP4tDxnGgFhy1kPesp3M

* test: keep two node tests disabled that crash on the testing build

test-vm-compile-function-lineoffset hits a V8 Smi::IsValid debug check and test-domain-error-types segfaults under --stress-compaction.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CfxP4tDxnGgFhy1kPesp3M

---------

Co-authored-by: Claude <noreply@anthropic.com>
(cherry picked from commit bcc5c51)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CfxP4tDxnGgFhy1kPesp3M