Karma BrowserStack reporting enhancements

[samirans89]

Current reporting ability of the Karma Launcher is only to mark status = 'failed' for a session. Does not handle success, timeouts, disconnect cases. Also, there is no provision added to mark failure reasons.  This PR implements the following changes:

• Handle additional Karma events for ‘spec complete’, ‘spec success’, ‘spec failure’, ‘spec skipped’, ‘browser complete’, ‘browser error’, ‘run complete’ for session reporting requirements 
• Update ‘Session Name’ with Karma ‘Test Suite name’ which got executed in the sessionUpdate session ‘Status’ field to ‘Passed’ or ‘Failed’ based on the actual session run
• Update the session ‘Reason’ field (255 chars) with the ‘specs completed’ within the session for ‘Passed’ runs and the first failure reason for ‘Failed’ runs
• Update ‘Build Name’ post batch execution of Karma tests with the number of specs passed, failed (if any) and also report whether the session encountered any disconnects / browser errors.

[googlebot]

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

:memo: Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.