build, doc: use new api doc tooling

[flakey5]

Switches over to using the new doc generation tooling. For more background on this, please see #52343

Currently a draft just to get feedback on the approach to this integration.

cc @nodejs/web-infra

---

Notable Change info (by @avivkeller):

The Node.js Website and Website Infrastructure teams have introduced a brand-new documentation pipeline, modernizing how our API docs are generated. While the documentation site may look familiar today, we are hard at work making a completely refreshed user interface in the very near future!

[nodejs-github-bot]

Review requested:

• @nodejs/nodejs-website
• @nodejs/web-infra

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.73%. Comparing base (9cc7fcc) to head (b313181).
⚠️ Report is 69 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #57343      +/-   ##
==========================================
+ Coverage   89.72%   89.73%   +0.01%     
==========================================
  Files         675      676       +1     
  Lines      204797   206069    +1272     
  Branches    39344    39519     +175     
==========================================
+ Hits       183752   184919    +1167     
+ Misses      13324    13302      -22     
- Partials     7721     7848     +127     

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

[ovflowd]

This is the result of many months of arduous work between many awesome folks, including @flakey5 @AugustinMauroy @araujogui @ovflowd @avivkeller and others.

I'm so proud of what we are achieving here and this is a huge step towards a modern tooling and a revamped API docs within Node.js

Approving, as I believe this is ready!

[lpinca]

RSLGTM because it is hard to review and outside of my comfort zone.

[nodejs-github-bot]

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

[ovflowd]

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[avivkeller]

I've resolved all the runner failures except for a few on Windows. I'll look at those today, we are going to get this merged!

[nodejs-github-bot]

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

[avivkeller]

There's quite honestly nothing else that could possibly fail

[nodejs-github-bot]

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

[nodejs-github-bot]

Landed in 76215dc

[Renegade334]

There's quite honestly nothing else that could possibly fail

A parting gift, then.

[Renegade334]

On a serious note, how far back are we intending this to land?

[avivkeller]

A parting gift, then.

It's a flake, and is not related to the changes in this PR. The test flaked twice before passing on it's third trial. See #61762

[avivkeller]

On a serious note, how far back are we intending this to land?

The plan is for this to land on all release lines, and immediately replace the existing documentation generation tooling, starting at the next patch release.

[aduh95]

There are some regressions in the JSON output (#57343 (comment)), let's not rush the backports