cleanup listener for user provided AbortSignal

[ronag]

Refs: whatwg/fetch#1287

[ronag]

The Request constructor will register an 'abort' listener we need to release at some point.

[ronag]

@benjamingr weak listeners would be nice here 😄

[flevi29]

This has been marked completed for a while now, and I assume node 18.10.0 uses the version of undici that has this issue marked as closed/completed. Running on 18.10.0 the code below gets me a MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit.

const ac = new AbortController();
for (let i = 0; i < 11; i += 1) {
  const response = await fetch("https://www.google.com", { signal: ac.signal });
  if (!response.ok) {
    throw new Error("For some reason fetch failed, make sure it doesn't");
  }
  console.log(i + 1);
}

I am writing a module for OAI-PMH lists which rely on fetching consecutively until a certain response is given. I want to be able to abort the current fetch with the same controller as I would have the previous, but currently that is not a good idea because fetch doesn't clean up the listener it registered on the signal it seems.
I guess I'll just let it leak for now, cause it does get cleaned up after fetching a whole list finishes.