Fix #1370

Add directive for providing saving updates to buttons 

Using transclusion allows for the directive to be set on an element
with non-trivial content and have that content nested inside the
status-button wrapper spans, but pre-bound to its lexical markup
scope.

Not sure we'll need it here, but I also wanted to see how one might
approximate 'replace' now that it's deprecated. The answer is by
not replacing but just adding the template you want after the passed
placeholder comment node.

This adds loading/success messages to a button for use with async
actions such as changing account information.

Search callback routing cleanup

The filtered copy list was not assigned back to the variable and
accidently we were comparing the value.length instead of the filter.terms.length
to check whether all tags have matched or not.

Improve usability of sheet tabs

This unifies the stream and page_search query parameter usage. Both now
use the 'q' parameter. Additionally, the search string is passed to
`simpleSearch` directive and the `QueryParser` instead of an object
with a "query" or "q" key.

The clump of conditionals in the route update event handler is removed.
Instead, the viewer and page search redirect to one another and the
stream can be totally ignorant of the involvement of the location.

The views are updated to use ?q= for /u and /t shortcuts.

Remove the drop shadow from the highlight states

Previously the active tab would be red, which could be confused with our
red anchor text and make the other tab look disabled. The new design
makes all text gray but adds an "active" border below the button.

Simplified search

Update from error styles based on feedback

Based on feedback from Dan that the plain red text is hard to
distinguish from hyper-links.

Tweak the HTML and CSS of the new search input.

Besides the line height hack for FF kill the rest of the px related
calculation and do everything in nice, pretty ems.

The trick used here was designed to honor the font setting in a user's
browser by assuming a typical default of 16px and computing the base
font size in ems relative to that.

The problem is that even if everything is sized in ems there are
sometimes aggressive user agent styles that complicate things by
restoring the system font. It turns out it fixes the various things
I've noticed in my FF this way.

This may fix the text issue displayed in FF with custom display
settings.

https://github.com/hypothesis/h/pull/1326#issuecomment-50655944

 * Remove the background color.
 * Borders and icon darken when the input is in focus.
 * Adds the placeholder text back.

Added a readable class name to the search icon .icon-search and
regenerated the icomoon css file.