feat(@angular/cli): allow for custom sha hash algos in SRI

[wkaskie]

PR Checklist

Please check to confirm your PR fulfills the following requirements:

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

PR Type

What kind of change does this PR introduce?

• Bugfix
• [ x ] 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?

Currently, enabling SRI will default to the sha384 algorithm. This is not always available on the server (s3 supports up to sha256, for example.)

Issue Number: 28946

What is the new behavior?

The modifications expose a new configuration property to match that of the webpack-subresource-integrity hashFuncNames which accepts an array of strings, leveraging the highest available. This allows users to set sha256 or sha512.

Does this PR introduce a breaking change?

• Yes
• [ x ] No

Other information

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[wkaskie]

I signed the CLA before creating the MR. Please advise.

[wkaskie]

I've updated the email address in the commit and made the email address public in my gitHub account

[wkaskie]

Closing to resubmit with the updated Author information

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