[v20.x backport] lib: remove settled dependant signals when they are GCed

[geeksilva97]

PR: #55354

[RedYetiDev]

Why? The original PR lands cleanly:

$ git cherry-pick 7a7c2b3d0953fa5a8bb69a5d865fce98e0c60669
Auto-merging lib/internal/abort_controller.js
[detached HEAD 7a3ea74466] lib: remove settled dependant signals when they are GCed
 Author: Edigleysson Silva (Edy) <[email protected]>
 Date: Mon Oct 14 17:33:41 2024 -0300
 2 files changed, 145 insertions(+), 9 deletions(-)
 create mode 100644 test/parallel/test-abortsignal-drop-settled-signals.mjs

[geeksilva97]

Why? The original PR lands cleanly:

$ git cherry-pick 7a7c2b3d0953fa5a8bb69a5d865fce98e0c60669
Auto-merging lib/internal/abort_controller.js
[detached HEAD 7a3ea74466] lib: remove settled dependant signals when they are GCed
 Author: Edigleysson Silva (Edy) <[email protected]>
 Date: Mon Oct 14 17:33:41 2024 -0300
 2 files changed, 145 insertions(+), 9 deletions(-)
 create mode 100644 test/parallel/test-abortsignal-drop-settled-signals.mjs

Hm, so it goes to lower versions? I didn't know that. Thanks for letting me know @RedYetiDev ! will close both.

[RedYetiDev]

For future reference, a backport is only needed if, when trying to prepare a release, a releaser can't cleanly apply a change. Most changes can be cleanly applied.