Fix/fs rmsync broken symlink 61020

[Han5991]

Summary

Fix fs.rmSync() so it correctly removes broken symbolic links (and symlinks to
directories) instead of becoming a no-op or throwing ERR_FS_EISDIR.

Fixes: #61020

Details

rmSync was using std::filesystem::status(), which follows symlinks. For
broken symlinks this reports not_found, causing rmSync to return early
without unlinking the symlink itself. Switching to std::filesystem::symlink_status()
makes rmSync operate on the symlink entry, matching fs.rm() behavior.

Tests

• ./node test/parallel/test-fs-rm.js

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.51%. Comparing base (4f24aff) to head (f7000b5).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #61040      +/-   ##
==========================================
- Coverage   88.53%   88.51%   -0.03%     
==========================================
  Files         703      703              
  Lines      208546   208546              
  Branches    40217    40222       +5     
==========================================
- Hits       184634   184590      -44     
- Misses      15926    15968      +42     
- Partials     7986     7988       +2     

Files with missing lines	Coverage Δ
src/node_file.cc	75.51% <100.00%> (-0.04%)	⬇️

... and 30 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.

[Renegade334]

This looks like the correct approach to me, we use lstat-based checks in rimraf etc.

Could you please squash your commits, so that the final commit message is the fs: one, not the test: one?