lib: use primordials in freelist.js

[Ayoub-Mabrouk]

Replace native methods with primordials for consistency and security. This improves protection against prototype pollution.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.53%. Comparing base (05d6b9b) to head (06d364e).
⚠️ Report is 1083 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #61208 +/- ##
==========================================
- Coverage 88.53% 88.53% -0.01% 
==========================================
Files 703 703 Lines 208599 208615 +16 Branches 40229 40252 +23 ==========================================
+ Hits 184685 184692 +7 - Misses 15939 15941 +2 - Partials 7975 7982 +7 

Files with missing lines	Coverage Δ
lib/internal/freelist.js	100.00% <100.00%> (ø)

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

[aduh95]

Duplicate of #36565, until proven otherwise we should expect this to perform poorly

Benchmark CI: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/1801/

 confidence improvement accuracy (*) (**) (***)
misc/freelist.js n=100000 *** -71.89 % ±0.70% ±0.95% ±1.26%
Be aware that when doing many comparisons the risk of a false-positive
result increases. In this case, there are 1 comparisons, you can thus
expect the following amount of false-positive results:
0.05 false positives, when considering a 5% risk acceptance (*, **, ***),
0.01 false positives, when considering a 1% risk acceptance (**, ***),
0.00 false positives, when considering a 0.1% risk acceptance (***)

[aduh95]

Performance regression makes it not worth it