fs: use getLazy for lazy loading

[gurgunday]

I think we can centralize the usage of lazy loading with the getLazy util in the codebase

Also before, we lazy loaded multiple modules even when we needed only one, so I believe splitting them further should be a little faster

It's cleaner and more consistent to use this everywhere

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.24%. Comparing base (1347d42) to head (f5c15c3).
Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #57307   +/-   ##
=======================================
  Coverage   90.24%   90.24%           
=======================================
  Files         630      630           
  Lines      184920   184928    +8     
  Branches    36188    36181    -7     
=======================================
+ Hits       166876   166889   +13     
+ Misses      11064    11063    -1     
+ Partials     6980     6976    -4     

Files with missing lines	Coverage Δ
lib/fs.js	98.28% <100.00%> (+<0.01%)	⬆️
lib/internal/util.js	95.80% <100.00%> (ø)

... and 37 files with indirect coverage changes

[joyeecheung]

I think lazy loading is only beneficial for APIs not commonly used by applications. Most of the APIs being changed here are very commonly used throughout the ecosystem and loading them eagerly keeps them in the snapshot, and would actually speed up loading of applications overall.