fix(@angular/ssr): abort web request signal when node request is aborted

[alan-agius4]

PR Checklist

Please check to confirm your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

When converting a Node.js IncomingMessage or Http2ServerRequest into a Web Request object in @angular/ssr, if the underlying Node request is aborted/closed prematurely, the Web Request object's signal does not abort.

What is the new behavior?

Connects an AbortController to the aborted event on the Node.js request so that the Web Request's signal is aborted whenever the incoming Node request is aborted.

Does this PR introduce a breaking change?

• Yes
• No

[gemini-code-assist]

Code Review

This pull request introduces abort handling for incoming Node.js requests by mapping the 'aborted' event to an AbortController signal on the created Web Request, with corresponding tests added for HTTP/1.1 and HTTP/2. Feedback suggests handling cases where the request is already aborted before the handler is registered, and cleaning up the event listener on 'close' to prevent potential memory leaks.