test: skip test-fs-cp* tests that are constantly failing on Windows

These tests are likely actual regressions introduced when the
monolithic test-fs-cp.mjs was marked as flaky and got ignored due
to the flaky status. They are now constantly failing the Windows
CI and require the CI to always be re-run on Windows when the job
is resumed. Simply skip them until someone fixes them, as there's
no point keep running these known regressions on Windows anymore.

PR-URL: #59637
Refs: #59636
Refs: #59408
Reviewed-By: Moshe Atlow <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Stefan Stojanovic <[email protected]>

Author: joyeecheung

test/parallel/parallel.status

@@ -24,11 +24,11 @@ test-snapshot-incompatible: SKIP
 test-async-context-frame: PASS, FLAKY
 # https://github.com/nodejs/node/issues/54534
 test-runner-run-watch: PASS, FLAKY
-# https://github.com/nodejs/node/pull/59408#issuecomment-3170650933
-test-fs-cp-sync-error-on-exist: PASS, FLAKY
-test-fs-cp-sync-symlink-points-to-dest-error: PASS, FLAKY
-test-fs-cp-async-symlink-points-to-dest: PASS, FLAKY
-test-fs-cp-sync-unicode-folder-names: PASS, FLAKY
+# https://github.com/nodejs/node/issues/59636
+test-fs-cp-sync-error-on-exist: SKIP
+test-fs-cp-sync-symlink-points-to-dest-error: SKIP
+test-fs-cp-async-symlink-points-to-dest: SKIP
+test-fs-cp-sync-unicode-folder-names: SKIP
 
 # https://github.com/nodejs/node/issues/56751
 test-without-async-context-frame: PASS, FLAKY