events: getMaxListeners detects 0 listeners

[KhafraDev]

With the removal of the max listeners warning from AbortSignal, a bug was surfaced with getMaxListeners.

> events.getMaxListeners(new AbortController().signal)
Uncaught:
TypeError [ERR_INVALID_ARG_TYPE]: The "emitter" argument must be an instance of EventEmitter or EventTarget. Received an instance of AbortSignal
    at Function.getMaxListeners (node:events:946:9) {
  code: 'ERR_INVALID_ARG_TYPE'
}

This causes performance issues for undici.

Refs: nodejs/undici#4032
Refs: c1ccade

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.21%. Comparing base (f2d2747) to head (5d43e31).
Report is 22 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #56807   +/-   ##
=======================================
  Coverage   89.21%   89.21%           
=======================================
  Files         663      663           
  Lines      192012   192012           
  Branches    36927    36928    +1     
=======================================
  Hits       171296   171296           
+ Misses      13586    13578    -8     
- Partials     7130     7138    +8     

Files with missing lines	Coverage Δ
lib/events.js	99.75% <100.00%> (ø)

... and 24 files with indirect coverage changes

[slagiewka]

Forgive my lack of process knowledge: what is the flow to make sure this gets backported to v22 (as it follows the backported change)? Should this PR have a label to be picked up?

[mcollina]

lgtm

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[lpinca]

@slagiewka, this can be backported once it has been on a Current release for at least two weeks, no label needed.

[nodejs-github-bot]

Landed in 752c0b8