Bug 1107279 - Improve consistency and layout of the job details pane

This work fixes Bugzilla bug [1107279](https://bugzilla.mozilla.org/show_bug.cgi?id=1107279).

@maurodoglio and others have seen this already in channel and like it, so I think this is ready for a PR. To improve the readability, consistency, and clarity of the job detail pane, we:

* convert the `glyphicon-star` because it's not a button
* make the bug link consistent with result sets (ie. no button border, regular anchor link, italic)
* remove the bug icon
* make the date format the same as the (recently changed and approved) date format in resultsets
* make the date and author more readable by putting them on individual lines
* style the date and author the same as our revision color grey `#777` for de-emphasis
* add a **Job**: prefix to the job field because that is what it is
* update a bunch of the tool tips to provide clarity
* add some padding tweaks for breathing space, when a job is classified and when it isn't
* remove the "Go to build directory" line, and linkify it as the build value*

Here's the before:

![jobdetailspanecurrent](https://cloud.githubusercontent.com/assets/3660661/5307634/d34c2f22-7bdc-11e4-9834-c0081fce1a45.jpg)

Here is the after:

![jobdetailspaneproposed](https://cloud.githubusercontent.com/assets/3660661/5307637/db45e6fa-7bdc-11e4-97cc-006e62d9aef2.jpg)

Here are a couple of the new tooltips:

![jobdetailspanetooltip](https://cloud.githubusercontent.com/assets/3660661/5307815/cf4837a2-7bde-11e4-8a3b-ef389a394e12.jpg)

![jobdetailspanetooltip2](https://cloud.githubusercontent.com/assets/3660661/5307816/d1ca40d8-7bde-11e4-8afe-b812017da5b6.jpg)

*note: the ng-switch to embed the linkfied value for the build directory, is the part I think needs to be exercised the most, to make sure it works with various jobs. I've tested it a bunch so far and it seems fine, but it would be handy for folks to try a few of their own to make sure that switch isn't suppressing or populating a line where it shouldn't.

I notice some infra failure jobs have bugs which aren't linked, but that is unrelated to this work.

Tested on Windows:
FF Release **33.1.1**
Chrome Latest Release **39.0.2171.71 m**

Adding @wlach and/or @camd for review and @edmorley for visibility.
Makes total sense to me. I'll one-way all the variables related to this particular return. Then I'd like to do the remainder in this file a separate commit along with a general clean up (comments, line lengths, markup separation).