process: move multipleResolves event to EOL

[jasnell]

The multipleResolves event has been deprecated for several years now. It's time.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.13%. Comparing base (3f6ad56) to head (1e3da65).

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #58707      +/-   ##
==========================================
- Coverage   90.15%   90.13%   -0.03%     
==========================================
  Files         637      637              
  Lines      188122   188062      -60     
  Branches    36886    36892       +6     
==========================================
- Hits       169595   169502      -93     
- Misses      11271    11317      +46     
+ Partials     7256     7243      -13     

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

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

[LiviaMedeiros]

Not blocking but IMHO this event should get Legacy status rather than being removed. Or we can keep it forever runtime deprecated (similar to how DEP0174 works) and make the warning message more descriptive.
Despite the false positives with Promise.race and Promise.all, it still can be useful for locating problems where code unintentionally keeps flowing after calling resolve() or reject().

If keeping this causes noticeable runtime overhead even when there's no listener (judging from this PR, it's just one boolean check per fired event?), +0 solely for performance reasons.

[Ethan-Arrowood]

LGTM

[Ethan-Arrowood]

Suggested change

	pr-url: https://github.com/nodejs/node/pull/00000
	pr-url: https://github.com/nodejs/node/pull/58707

[Ethan-Arrowood]

Suggested change

	This event was deprecated and remove because it did not work with V8 promise
	This event was deprecated and removed because it did not work with V8 promise