created the charmbrowser view and have the new curated result list rendering into it

token is highlighted when being clicked on

Make headers sticky and fix the position of the spinner
Added charmbrowser view test file and tests
Cache unit tokens internally for easy rendering.

Switch unplaced service unit tokens to function in the same manner as
machine tokens. They're stored in a cache by ID and when a DB change
comes in we grab the correct token and re-render it.
Merge pull request #339 from kadams54/unit-token-rendering

### QA

With `/:flags:/il/mv`.

1. Deploy the Wikimedia bundle.
2. Drag-n-drop the Wordpress charm over, but don't deploy it.
3. Switch to machine view.
4. Run this in your console:
~~~~
var u = app.db.units.item(2), m = app.db.units.revive(u); m.set('machine', '0');
~~~~

You should see the Wordpress icon added to the 0 machine and removed from the unplaced units column. Additionally the "All units placed" message should appear.
Merge pull request #338 from hatched/consolidate-browser

This is the first step of a few branches to consolidate the editorial code and search results code into a single `charmbrowser.js` view.

#### Notes
- `editorial` has been renamed to `curated`
- There is an existing bug in develop where the `home` button does not work in the charm search results. This bug still exists in this branch.
- Charm results cache has been removed but there is a card to implement a new version this cycle.
- The old files will be removed as a last step so this only includes the new code.

#### To QA
- Use the il flag (but it should still work fine without)
- Do exploratory QA on the curated results. It should all function the same as before.
Relation lines rerender when service block type changes
Fleshing out test description
Adding messages to asserts
Lint fix.
Merge pull request #340 from makyo/sub-rels-2

As subordinate status is not included in bundles, the type of service block changes after deploying a bundle as soon as subordinate information is populated in the db.  This propagated to services, but not to relations.

To QA: search for 'complex' and deploy that bundle.  Once subordinate information is populated in the db, the relations should turn gray.
Destroy service inspector when service is destroyed
Changed asserts per review.
Merge pull request #343 from makyo/destroy-inspector

To QA:

With and without il flag, deploy a service, then destroy it; the inspector should be destroyed as well.