test: unmark exit timeout tests as flaky

Background compilation could deadlock at process exit: DrainTasks
waited for the compiler task while that task waited for main-thread
garbage collection. Since 5fb879c, only user-blocking tasks count
toward that wait, excluding ordinary background compilation.

Remove the old flaky expectations for test-http2-large-file and
test-fs-read-stream-concurrent-reads.

Refs: #47409
Refs: #51862
Refs: #54918
Signed-off-by: Filip Skokan <panva.ip@gmail.com>
Assisted-by: Claude, Codex
PR-URL: #66319
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>

Author: panva

test/parallel/parallel.status

@@ -9,9 +9,6 @@ prefix parallel
 test-shadow-realm-gc: SKIP
 test-shadow-realm-gc-module: SKIP
 
-# https://github.com/nodejs/node/issues/51862
-test-fs-read-stream-concurrent-reads: PASS, FLAKY
-
 # Until V8 provides a better way to check for flag mismatch without
 # making the code cache/snapshot unreproducible, disable the test
 # for a preemptive check now. It should ideally fail more gracefully

test/sequential/sequential.status

@@ -5,8 +5,6 @@ prefix sequential
 # sample-test                       : PASS,FLAKY
 
 [true] # This section applies to all platforms
-# https://github.com/nodejs/node/issues/47409
-test-http2-large-file: PASS, FLAKY
 
 [$system==win32]
 # https://github.com/nodejs/node/issues/63212#issuecomment-5423558796