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 79.09091% with 184 lines in your changes missing coverage. Please review.

Project coverage is 90.04%. Comparing base (462c741) to head (8ba4c08).
Report is 81 commits behind head on main.

Files with missing lines	Patch %	Lines
src/node_locks.cc	68.92%	100 Missing and 70 partials ⚠️
lib/internal/locks.js	95.22%	14 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #58666      +/-   ##
==========================================
- Coverage   90.15%   90.04%   -0.12%     
==========================================
  Files         639      643       +4     
  Lines      188201   189311    +1110     
  Branches    36915    37139     +224     
==========================================
+ Hits       169675   170463     +788     
- Misses      11274    11506     +232     
- Partials     7252     7342      +90     

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	68.92% <68.92%> (ø)

... and 89 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)

[IlyasShabi]

@jasnell I fixed all your comments in the last commit, can you take a look and rerun the CI?
FYI a couple of WPT tests were flaky on linuxone RHEL 8/9 machines, I cleaned them all up - let’s see what the CI says 🤞

[github-actions]

The notable-change PRs with changes that should be highlighted in changelogs. label has been added by @anonrig.

Please suggest a text for the release notes if you'd like to include a more detailed summary, then proceed to update the PR description with the text or a link to the notable change suggested text comment. Otherwise, the commit will be placed in the Other Notable Changes section.

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[jasnell]

If Then returns an empty, then v8 will have already scheduled an error. You can probably use a v8::TryCatch in here and reject the waiting_promise() and released_promise() with it's Exception(), but you'd want to check CanContinue() first.

[IlyasShabi]

Done

[jasnell]

Just putting the red x on this since CI passed and it has sufficient sign off from others to land but there are still a few outstanding issues to resolve. I want to make sure it doesn't end up getting landed by the commit-queue while some comments are still pending.

[nodejs-github-bot]

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

[jasnell]

These's aren't correct here. You really should not be holding a v8::Global<T> inside a v8::External, then deleting it like this. It's fine to use indirection through another type... e.g. having the External hold an instance of a struct that is holding the Global<T>.

[jasnell]

I still think there may be at least a few issues here relating to how you're using v8::Global and v8::External. I'd really like to see if we could get @addaleax to take a look.