Single/Multiline Build History

Main changes:

1. A more dynamic build history layout. This is the main change. See screenshot below.
2. Left side-panel is now a fixed width for screens wider than 768px i.e. does not keep resizing as the screen width changes. 

__Note__: You can download and try the [jenkins.war from the CI build of this PR](https://jenkins.ci.cloudbees.com/job/core/job/jenkins-core/1738/artifact/war/target/jenkins.war).

![screenshot 2014-11-26 14 25 31](https://cloud.githubusercontent.com/assets/429311/5202695/1edd2d9e-7578-11e4-9837-9a858c5c3f2b.png)

It puts all build details on a single line so long as none of the fields in the row overflow. If any of them overflow, it converts the row to be "multi-line" and then tries moving the data around to make it fit:

1. It tries to put the build name and "controls" (stop, badges etc) on the first row of the multi-line, moving the "build-details" (date etc) down to a line of it's own.
2. If #1 above fails (build name is too long), it gives all of the first line in the multi-line to the build name (wrapping if needed) and then tries fitting the "build-details" (date etc) and "controls" (stop, badges etc) together on the second row. .
3. If #1 and #2 above fail (both name and details are too long), it gives a row to each of name, details and controls (stop, badges etc - if there are any), again wrapping as needed.
4. If there are badges and they overflow, they too will be moved to a line of their own. See screenshot below.

Build descriptions are always given a full line of their own, creating a multi-line.