Karma master timeout

From an inaccurately small window of 4 hours, we seem to average 0.75 failures/hr on karma. This seems new to me, especially considering karma has only gotten lighter this week.

I've grouped these for now in case there is some global approach we can take.

@winh should I go ahead and open these as separate issues or do you think something could be happening globally?

https://gitlab.com/gitlab-org/gitlab-ee/-/jobs/185024683:

FAILED TESTS:
  Split security reports app
    with all reports
      ✖ renders all reports collapsed by default
        Chrome
      Failed: Test is running too long!
          at webpack:///builds/gitlab-org/gitlab-ee/spec/javascripts/test_bundle.js:113 <- spec/javascripts/test_bundle.bundle.js:1980064:10

TOTAL: 1 FAILED, 8940 SUCCESS

https://gitlab.com/gitlab-org/gitlab-ee/-/jobs/184998353:

FAILED TESTS:
  ee merge request widget options
    code quality
      with empty successful request
        ✖ should render provided data
          Chrome
        Failed: Test is running too long!
            at webpack:///builds/gitlab-org/gitlab-ee/spec/javascripts/test_bundle.js:113 <- spec/javascripts/test_bundle.bundle.js:1980064:10

TOTAL: 1 FAILED, 8940 SUCCESS

https://gitlab.com/gitlab-org/gitlab-ee/-/jobs/184976171:

FAILED TESTS:
  Grouped security reports app
    with all reports
      ✖ opens modal with more information
        Chrome
      Failed: Test is running too long!
          at webpack:///builds/gitlab-org/gitlab-ee/spec/javascripts/test_bundle.js:113 <- spec/javascripts/test_bundle.bundle.js:1964812:10

TOTAL: 1 FAILED, 8892 SUCCESS