test: add fs.rmSync regression test for Unicode filename crash on Windows

[nabeel378]

Adds a regression test for a Windows-specific bug where fs.rmSync('速') crashes without throwing, observed in Node.js v23.3.0.

• Reproduces the issue in a controlled test.
• Skips the test on non-Windows platforms.
• Does not crash on older versions or Linux/macOS.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.10%. Comparing base (04cb572) to head (0836b0e).
Report is 57 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #58884      +/-   ##
==========================================
+ Coverage   90.07%   90.10%   +0.02%     
==========================================
  Files         640      640              
  Lines      188262   188493     +231     
  Branches    36912    36966      +54     
==========================================
+ Hits       169580   169842     +262     
+ Misses      11399    11358      -41     
- Partials     7283     7293      +10     

see 67 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

Failed to start CI

   ⚠  No approving reviews found
   ✘  Refusing to run CI on potentially unsafe PR

https://github.com/nodejs/node/actions/runs/15994275556

[StefanStojanovic]

Hey @nabeel378, thanks for the effort. From what I understand, this test will fail with the current Node.js implementation - it will not throw an error, and asserting fs.existsSync will fail. Correct?

[nabeel378]

Hey @nabeel378, thanks for the effort. From what I understand, this test will fail with the current Node.js implementation - it will not throw an error, and asserting fs.existsSync will fail. Correct?

HI @StefanStojanovic,
Yes , it should throw an error. This is related to issue #56049.