build: upgrade karma to version 4.4.0

[bjarkler]

Upgrade the karma dependency to version 4.4.0 in the root package.json
and in integration tests. Compared to version 4.3.0, which most of the
packages were previously depending on, it has the following changes:

Bug Fixes

• runner: remove explicit error on all tests failed

Features

• client: Add trusted types support
• Preprocessor can return Promise
• config: add failOnSkippedTests option.
• config: clientDisplayNone sets client elements display none.
• deps: Remove core-js dependency.

The motivation for upgrading the package is the Trusted Types support
that it adds, which is necessary to enable Trusted Types in Angular's
unit tests.

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• 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
• angular.io application / infrastructure changes
• Other... Please describe:

Does this PR introduce a breaking change?

• Yes
• No

[josephperrott]

LGTM

Reviewed-for: dev-infra

[bjarkler]

CC @engelsdamien @koto

[AndrewKushnir]

@josephperrott would it make sense to update the required SHA here https://github.com/angular/angular/blob/master/.ng-dev/merge.ts#L24 as well once this PR lands?

[josephperrott]

@AndrewKushnir Yeah, we can update it since it changes the runner.

[AndrewKushnir]

Thanks @josephperrott, I'll take care of creating a new PR to update required base SHA once this PR lands.

[AndrewKushnir]

FYI, I've rebased this PR on top of the current version of the master branch, since the deploy_aio CircleCI job was failing, will see if it's resolved after rebase.

[josephperrott]

@AndrewKushnir I will work on a fix now, but the failure for deploy_aio was caused by the job running without the expected PR contexts.

[IgorMinar]

LGTM

@AndrewKushnir I think the risk for regressions caused by non-rebased in-flight PRs is very low since we are not actually turning the trusted types support on in this PR, so I recommend waiting for the follow up PR that will turn TT support on in karma and only then updating the required rebase SHA.

[IgorMinar]

quick note on the PR target: while we don’t need this in the RC branch, in order to minimize the diff between the master branch and the 10.0.x branch, it might be a good idea to retarget this as target: rc.

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