doc: allow the $schema property in node.config.json

[remcohaszing]

The documentation states people can use the $schema property, but the JSON schema forbids this. This change allows it.

[nodejs-github-bot]

Review requested:

• @nodejs/config

[marco-ippolito]

Good catch thanks!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.25%. Comparing base (5a7b7d2) to head (6388137).
Report is 7 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #57560      +/-   ##
==========================================
+ Coverage   90.24%   90.25%   +0.01%     
==========================================
  Files         630      630              
  Lines      185013   185017       +4     
  Branches    36241    36240       -1     
==========================================
+ Hits       166966   166991      +25     
+ Misses      10998    10993       -5     
+ Partials     7049     7033      -16     

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

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

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[remcohaszing]

I’m confused by the unsuccessful checks. Is this something I need to fix or are those checks just unstable?

For example I ended up at https://ci.nodejs.org/job/node-test-commit-linux-containered/49686/nodes=ubuntu2204_sharedlibs_openssl32_x64/testReport/(root)/pummel/test_buffer_large_size/

---
duration_ms: 720105.64
exitcode: -15
severity: fail
stack: |-
  timeout
  (node:3777203) [DEP0030] DeprecationWarning: SlowBuffer() is deprecated. Please use Buffer.allocUnsafeSlow()
  (Use `node --trace-deprecation ...` to show where the warning was created)
...

[marco-ippolito]

just flaky test 😄