util: show SuppressedError's error/suppressed properties on inspect

[agape1225]

util.inspect() (and console.log()) silently dropped a SuppressedError's error and suppressed properties, the two pieces of information needed to actually debug a disposal failure. Both properties are non-enumerable, so they never showed up without this.

formatError() already special-cases two other non-enumerable "container" properties for the same reason: Error's cause (#41002) and AggregateError's errors (#43646). Handle SuppressedError's error and suppressed the same way; nested SuppressedErrors (from multiple failed disposals) are shown recursively since inspect() already recurses into any Error-valued property.

Fixes: #66033

[codecov]

Codecov Report

❌ Patch coverage is 90.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 90.28%. Comparing base (25e6c15) to head (0f7d877).
⚠️ Report is 21 commits behind head on main.

Files with missing lines	Patch %	Lines
lib/internal/util/inspect.js	90.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #66159      +/-   ##
==========================================
+ Coverage   90.27%   90.28%   +0.01%     
==========================================
  Files         790      790              
  Lines      271981   271991      +10     
  Branches    51913    51948      +35     
==========================================
+ Hits       245531   245574      +43     
+ Misses      16945    16905      -40     
- Partials     9505     9512       +7     

Files with missing lines	Coverage Δ
lib/internal/util/inspect.js	97.04% <90.00%> (-0.03%)	⬇️

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

[ljharb]

why not:

Suggested change

	const custom = new Error('No own error/suppressed property');
	Object.setPrototypeOf(custom, suppressedError);
	const custom = new SuppressedError('No own error/suppressed property');

?

[agape1225]

Thanks for the suggestion! I'd like to keep the original version, though — SuppressedError's signature is (error, suppressed, message), so with just one argument that string becomes error, not the message, and both error/suppressed end up as own properties (same as cause above). That means it wouldn't exercise the 'no own property' case this block is meant to test. Happy to tweak the comment or naming if that'd help.

[nodejs-github-bot]

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