refactor(@schematics/angular): remove copyright header from universal schematic files

[brandonroberts]

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?

Angular copyright headers are included in scaffolded files when adding Angular Universal support.

Issue Number: N/A

What is the new behavior?

The Angular copyright headers are no longer included in scaffolded files when adding Angular Universal support.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[ngbot]

I see that you just added the action: merge label, but the following checks are still failing:
     status "ci/circleci: e2e-cli-npm" is failing
     status "ci/circleci: e2e-cli-yarn" is failing
If you want your PR to be merged, it has to pass all the CI checks.
If you can't get the PR to a green state due to flakes or broken main, please try rebasing to main and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

[alan-agius4]

@brandonroberts, thanks for this.

[dgp1130]

@brandonroberts there was a CI issue with a recent update to lru-cache which should now be fixed. I think if you rebase CI should pass?

[dgp1130]

Thanks @brandonroberts, merged it in!

[brandonroberts]

Thanks @dgp1130!

[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.}