inspector: initial support for Network.loadNetworkResource

[islandryu]

Fixes: #57873

Adds initial support for Network.loadNetworkResource in the inspector.
https://chromedevtools.github.io/devtools-protocol/tot/Network/#method-loadNetworkResource

how to load network resource

Resource fetching is done via a spawned child process to keep the inspector's event loop clean and isolated.
The JavaScript code for the fetch process is currently hardcoded, which may not be ideal, but I couldn't come up with a better approach at this point.

When --experimental-inspector-network-resource is set, a dedicated worker for loadNetworkResource is launched.
This worker fetches the resource and returns the result to the frontend.
https://github.com/nodejs/node/pull/58077/files#diff-5d3d58cbcfda008f49966a11d73863e67b78a237aa386f1fbdc5c9124136c1eb

check the behavior in chromium

To verify this change in Chromium, modify the section in the link as shown below and launch Chromium with the built DevTools frontend.

https://source.chromium.org/chromium/chromium/src/+/main:third_party/devtools-frontend/src/front_end/core/sdk/Target.ts;l=87-88

      case Type.NODE:
        this.#capabilitiesMask = Capability.JS | Capability.NETWORK | Capability.TARGET | Capability.IO;

# open Chromium with built devtools-frontend
Chromium --custom-devtools-frontend=(file path)

other infomation

If this change is considered acceptable, I will send a follow-up change request to expand the Node.js DevTools target with IO support.
If it is necessary to wait until Network.loadNetworkResource becomes stable in CRDP, please feel free to keep this PR pending.

[nodejs-github-bot]

Review requested:

• @nodejs/config
• @nodejs/gyp

[codecov]

Codecov Report

Attention: Patch coverage is 91.92547% with 13 lines in your changes missing coverage. Please review.

Project coverage is 90.06%. Comparing base (0992d28) to head (04d8eca).
Report is 8 commits behind head on main.

Files with missing lines	Patch %	Lines
lib/internal/inspector/network_resources.js	77.77%	6 Missing ⚠️
src/inspector/network_agent.cc	85.18%	2 Missing and 2 partials ⚠️
src/inspector_js_api.cc	72.72%	0 Missing and 3 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #58077      +/-   ##
==========================================
- Coverage   90.06%   90.06%   -0.01%     
==========================================
  Files         641      645       +4     
  Lines      188846   188996     +150     
  Branches    37049    37063      +14     
==========================================
+ Hits       170087   170211     +124     
- Misses      11476    11488      +12     
- Partials     7283     7297      +14     

Files with missing lines	Coverage Δ
lib/inspector.js	97.04% <100.00%> (+0.10%)	⬆️
src/inspector/io_agent.cc	100.00% <100.00%> (ø)
src/inspector/io_agent.h	100.00% <100.00%> (ø)
src/inspector/network_agent.h	100.00% <ø> (ø)
src/inspector/network_inspector.cc	90.90% <100.00%> (+0.90%)	⬆️
src/inspector/network_inspector.h	100.00% <ø> (ø)
src/inspector/network_resource_manager.cc	100.00% <100.00%> (ø)
src/inspector/worker_inspector.cc	95.89% <100.00%> (+0.05%)	⬆️
src/inspector/worker_inspector.h	100.00% <100.00%> (ø)
src/inspector_agent.cc	79.91% <100.00%> (+0.33%)	⬆️
... and 6 more

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

[islandryu]

@legendecas cc: @joyeecheung
I made changes to spawn a worker process for fetching.
It’s also possible to change it so that this behavior is delegated to the user via the Inspector JS API.
However, since the worker needs to be launched before the entry file is loaded in order to resolve source maps for Chrome DevTools, this part likely cannot be delegated to the user.

[islandryu]

The implementation approach was significantly changed in commit ce745ca.
I talked with @legendecas, and we decided to adopt an implementation that only returns resources that were preemptively put, as it requires less consideration in terms of security and implementation complexity.

[legendecas]

Thanks for the work! The new approach looks more straightforward as a first step to me.

[legendecas]

Thank you! Some minor suggestions..

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[github-actions]

Failed to start CI

   ⚠  Commits were pushed since the last approving review:
   ⚠  - inspector: initial support for Network.loadNetworkResource
   ⚠  - format
   ⚠  - fix build error
   ⚠  - fix unusual chars
   ⚠  - remove unix.h
   ⚠  - fix namespace
   ⚠  - fix lint
   ⚠  - fetch network resource on worker thread
   ⚠  - format
   ⚠  - format
   ⚠  - fix build error
   ⚠  - put method api
   ⚠  - remove comment
   ⚠  - avoid making networkResourceManager a static class.
   ⚠  - format
   ⚠  - add mutex lock to NetworkResourceManager
   ⚠  - Update src/inspector/network_agent.cc
   ⚠  - use url as stream id
   ⚠  - fix test
   ⚠  - fix lint
   ⚠  - use std::optional
   ⚠  - add flag to manpage
   ✘  Refusing to run CI on potentially unsafe PR

https://github.com/nodejs/node/actions/runs/16067992462

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

Landed in b7db89f