perf_hooks: add missing resource timing attributes

[greenheadHQ]

Add the PerformanceResourceTiming attributes from the Resource Timing specification that are still missing in Node.js: finalResponseHeadersStart, firstInterimResponseStart, renderBlockingStatus, contentType, and contentEncoding.

The new getters follow the existing PerformanceResourceTiming pattern and are included in toJSON(). The WPT status file is updated to enable the ten idlharness subtests that now pass.

Update responseStart to return firstInterimResponseStart when it is non-zero and fall back to finalResponseHeadersStart otherwise, matching the Resource Timing specification.

Tests cover the new getters, default and supplied metadata, the interim = 0, final > 0 fallback, and an entry created by the built-in fetch() implementation.

Refs: #51589

[nodejs-github-bot]

Review requested:

• @nodejs/web-standards

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.07%. Comparing base (31cde9f) to head (e0e7844).
⚠️ Report is 470 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #65017      +/-   ##
==========================================
- Coverage   90.30%   90.07%   -0.23%     
==========================================
  Files         759      754       -5     
  Lines      247621   256399    +8778     
  Branches    46672    48495    +1823     
==========================================
+ Hits       223603   230948    +7345     
- Misses      15473    16582    +1109     
- Partials     8545     8869     +324     

Files with missing lines	Coverage Δ
lib/internal/perf/resource_timing.js	99.67% <100.00%> (+0.04%)	⬆️

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

[greenheadHQ]

Hello @legendecas @jasnell 🖐️

Thank you for all the work that goes into reviewing contributions here! Just a gentle ping in case this PR slipped through the cracks. I would appreciate any feedback whenever you have time, no rush at all. Thanks!

[daeyeon]

The added test shows that this property can return a non-zero value even though interim responses are not currently recorded.

assert.strictEqual(resource.firstInterimResponseStart, 45);

This mixes the API's capabilities with current Node.js behavior. The other added properties appear to have the same issue.

[greenheadHQ]

Thanks, I missed that distinction. I updated the affected docs to separate the API behavior from the values currently produced by built-in fetch().