Hide possible culprits on "claimed" builds
Build Monitor functionality can be verified with browser-based tests.

Initial work to enable integration (see #51) and acceptance testing.
SauceLabs repository needs to be present in the pom.xml for the jenkins build to commence.
Acceptance tests running on SauceLabs can be configured using env variables.
Skipping the acceptance test for now until communication between CloudBees Jenkins and SouceLabs works correctly
It should be now possible to run Selenium-based tests on CloudBees Jenkins
SauceLabs test reports names are human readable
Another small step on the way of enabling browser-based integration and acceptance testing. #51
Ignoring the BFA acceptance test for now as it's experiencing issues with timing when executed on SauceLabs.
Acceptance tests should run correctly on sauce labs

Closes #41 and #51
Merge pull request #49 from drekbour/claimed-build

List of possible culprits is only displayed on failing, "unclaimed" builds.
The decision of whether or not indicate culprits on claimed builds is now moved to the back-end. This was this behaviour could be made configurable.

Addresses #40 and #49
Improved the font sizing based on feedback on twitter. Thanks @echohack!

https://twitter.com/echohack/status/474842522800250881
Readme reflects current look of Build Monitor
Readme: corrected a typo
Feature: Build Monitor supports Cloudbees Folder plugin.

This change set closes #50 and #66, thanks to @suryagaddipati and @daniel-beck for their help and suggestions.

Please also note that this change requires Jenkins 1.532 or later.
Chore: upgraded JavaScript testing libs
Chore: upgraded maven-karma-plugin as it allows to specify karma executable that's not installed globally
Chore: Added other karma dependencies that need to be installed locally
Fix: Build Monitor displays correctly on the latest Jenkins 1.572 using its div-based, re-written UI.