[npm] upgrade karma

[spalger]

There have been a lot of chrome instances left running on Jenkins slaves, and based on the ps output they all seem to be instances started by karma. In an effort to fix that I realized our karma deps were pretty out of date.

For instance, after this test failure: https://kibana-ci.elastic.co/job/elastic+kibana+pull-request+multijob-intake/6921/

The box looked like this:

[tylersmalley]

Getting 3 failed tests locallyChrome 58.0.3029 (Mac OS X 10.11.6): Executed 2950 of 2956 (3 FAILED) (skipped 6) (2 mins 47.749 secs / 31.792 secs)

Chrome 58.0.3029 (Mac OS X 10.11.6) tag cloud tests should only send single renderComplete event at the very end, using 500ms timeout positions should be ok FAILED
	TypeError: Cannot read property '1' of undefined
	    at shouldAssert (http://localhost:5610/bundles/tests.bundle.js:536089:28)
	    at Context.<anonymous> (http://localhost:5610/bundles/tests.bundle.js:536103:13)
	    at <anonymous>
Chrome 58.0.3029 (Mac OS X 10.11.6) tag cloud tests should not get multiple render-events "before each" hook for "positions should be ok" FAILED
	Error: the string "Should not get multiple render events" was thrown, throw an Error :)
	    at <anonymous>

[spalger]

@tylersmalley dependably? I know the tag cloud tests have been somewhat flaky in the past, and they're passing here and on Jenkins

[tylersmalley]

@spalger, running again

[tylersmalley]

@thomasneirynck, are these tests a known issue? Or are they considered stable now?

[tylersmalley]

These tests pass locally for me if I use the test:browser-ci task but I always get 3-4 failures when using test:browser. Seeing if this is also happening on master.

[tylersmalley]

It appears this is consistent with master and this PR does not seem to introduce any more failures.

[tylersmalley]

LGTM

[spalger]

5.5/5.x: 128be20
5.4: 154f52a

[thomasneirynck]

@tylersmalley Those tagcloud test failures in this PR are not a known issue right now. They were flaky about 6 months ago, but should have been resolved since (#9251). So if these failures are popping up again, we should investigate. Right now, Master, 5,x, 5.4 seem to be green though..