fix(@schematics/angular): rename SSR port env variable

[9kubczas4]

Rename SSR port env variable to SSR_PORT.

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?

Issue Number: N/A

What is the new behavior?

Rename the SSR port env variable to SSR_PORT.
It could help to resolve this firebase issue: firebase/firebase-tools#6651 (comment), cause PORT is reserved environment variable: https://firebase.google.com/docs/functions/config-env?gen=2nd#reserved-names.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[alan-agius4]

Can you also please add more context in the commit body? Example:
Linking to firebase/firebase-tools#6651 (comment) and explaining that PORT is reserved variable as per https://firebase.google.com/docs/functions/config-env?gen=2nd#reserved-names?

Additionally the scope should be @schematics/angular, the type can also be a fix.

[inlined]

This actually breaks Firebase on deploy. PORT is a reserved variable because it's what Functions and Run uses to set the port to listen to. Let's collaborate on a working solution.

[alan-agius4]

@inlined, should we revert this?

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}