src: add web locks api

[IlyasShabi]

This PR implements the Web Locks API, Locks are used to coordinate access to shared resources across multiple threads.

This implementation is based on previous work in #22719 and #36502, but takes a C++ native approach for better performance and reliability, this solution uses a singleton LockManager with thread-safe data structures to coordinate locks across all workers.

• Support exclusive and shared modes
• Support steal option
• Support ifAvailable option
• Support signal option
• Documentation
• WPT tests
• Add missing query.https.any.js tests as unit tests
• Add basic tests

Closes: #22702
Refs: https://w3c.github.io/web-locks

[nodejs-github-bot]

Review requested:

• @nodejs/gyp
• @nodejs/startup
• @nodejs/web-standards

[codecov]

Codecov Report

Attention: Patch coverage is 85.87786% with 111 lines in your changes missing coverage. Please review.

Project coverage is 90.09%. Comparing base (462c741) to head (9ee6d05).
Report is 20 commits behind head on main.

Files with missing lines	Patch %	Lines
src/node_locks.cc	78.68%	52 Missing and 45 partials ⚠️
lib/internal/locks.js	95.22%	14 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #58666      +/-   ##
==========================================
- Coverage   90.15%   90.09%   -0.07%     
==========================================
  Files         639      643       +4     
  Lines      188201   189085     +884     
  Branches    36915    37077     +162     
==========================================
+ Hits       169675   170355     +680     
- Misses      11274    11420     +146     
- Partials     7252     7310      +58     

Files with missing lines	Coverage Δ
lib/internal/navigator.js	99.37% <100.00%> (+0.04%)	⬆️
lib/worker_threads.js	100.00% <100.00%> (ø)
src/node_binding.cc	82.67% <ø> (ø)
src/node_external_reference.h	100.00% <ø> (ø)
src/node_locks.h	100.00% <100.00%> (ø)
lib/internal/locks.js	95.22% <95.22%> (ø)
src/node_locks.cc	78.68% <78.68%> (ø)

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

[mcollina]

lgtm

[Ethan-Arrowood]

this lgtm. I looked through the WPT and other tests and they look all good. I reviewed the JS api to make sure it aligns with expectations and analyzed its source. All is good for a first implementation. I did a cursory review of the C++ part as I'm less experienced there, but in general it looks okay too. Nice work!

[panva]

Adding semver-major PRs that contain breaking changes and should be released in the next major version. as this adds new globals (Lock, LockManager)

[panva]

@IlyasShabi can you rebase so that we can start CI?

[IlyasShabi]

@panva can you run the CI again?

[BridgeAR]

There seems to be a related test failure on linuxone. I didn't look closer into the code, so I can't tell why: https://ci.nodejs.org/job/node-test-commit-linuxone/50100/

[targos]

To avoid semver-major and allow early testing, this could be exposed from a builtin module and only added as a global later.

[IlyasShabi]

@targos I remove it from globals, could you please replace semver-major by semver-minor

[jasnell]

The CI test failures are not flaky failures. Before running the CI again on this the relevant failures should be looked at

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/67595/