Adding ghost relations.

Relations are now added to changeset.
Responding to reviews

* Move ecs flag to mv
* Do not modify changeset in place
* Add comments
Tests updated to reflect new _buildHierarchy behavior.
Make prep
Comments added around JSON.stringify
Updated new state object to use filter object to support text and category searches.

Filter needs to be updated on buildQueryPart
Clicking autocomplete takes you to the charm
Plug in deploy button with a temporary event.
Responding to reviews: using stub methods, using halt instead of preventDefault
Removing excess .only
Sidebar scrollbar should be always visible so the content doesn't jump around.
Merge pull request #258 from jaycee/charm-search-state

This updates the state object to work with autocomplete's categories and charms.

* The state object now updates its already existing filter model based on what's
  in metadata.search, which now holds the filter object generated by search
  code.
* The presence of a filter object in metatdata.search, as well as the
  filter.replace and filter.clear properties, determines whether the state is
  handling a search, which determines the generation of a query string.
* The state object is built from the query object if there is a text property or
  a categories property--either of these indicate a search has been input.
* The search and view code have been updated to set the right data on metadata
  based on the change object. The search widget did not have to be changed for
  this--the change object it generates, which is necessary without the flag, is
  used by the other code. This can be cleaned up when we remove the old state
  object and viewNagivate events.

QA 

Test with and without the il flag.

1) Search for 'apache'; click on a charm provided by the autocomplete.
2) You should open the details for the charm as well as populate the search
   text.

3) click the search box to bring up the categories. Click one.
4) You should get a search result for the category, with an updated
   querystring.
Merge pull request #259 from makyo/deploy-onclick

Test with the mv flag. 

* Drag a service onto the canvas
* Click deploy in the inspector
* Click deploy in the deployer bar - the service should deploy
Merge pull request #260 from huwshimi/sidebar-scrollbar-visible

Sidebar scrollbar should be always visible so the content doesn't jump around.
Realign inspector breakout panel to come from left

This is a first step. The changes here break some of the ideas of the
viewlet-manager and viewlets. There are work arounds in place here so that we
can move forward and discuss how to adjust to the requirements here.

- Updates the unit and service details to come into the same space as charm
details.
- Works around the issue of the close event not being in the same dom tree as
the viewlet-manager and not caught to close the breakout panels.
- Updates the css for the new location.

QA
---

- make devel
- view the site with :flags:/il
- deploy a service and once it's deployed, click on the "Charm details" link and
  a functional details popout should appear.
- Close and verify it closes properly and reopens as well.
- Go to a running unit and select the unit to open its details.
- Verify you can go straight from a unit to a service details and back/forth
  without issue.
- Verify that with a panel open, if you close the inspector the panel also
  closes.
- Verify that the inspector and panels work without the feature flag as
  expected.
Merge pull request #253 from makyo/relation-ecs

Relations are now added to changeset.

To QA: use flags ecs and mv

* Drag mysql and wordpress onto the canvas.
* click deploy once for each
* long-click and add a relation between the two - the relation line will disappear
*  Ensure that the relation is in the changeset by investigating app.ecs.changeSet in the javascript console.
* Run app.ecs.commit(), ensure that the relation is in the database.
Merge pull request #261 from mitechie/qa-inspector-panels

This is a first step. The changes here break some of the ideas of the
viewlet-manager and viewlets. There are work arounds in place here so that we
can move forward and discuss how to adjust to the requirements here.

- Updates the unit and service details to come into the same space as charm
details.
- Works around the issue of the close event not being in the same dom tree as
the viewlet-manager and not caught to close the breakout panels.
- Updates the css for the new location.

QA
---

- make devel
- view the site with :flags:/il
- deploy a service and once it's deployed, click on the "Charm details" link and
  a functional details popout should appear.
- Close and verify it closes properly and reopens as well.
- Go to a running unit and select the unit to open its details.
- Verify you can go straight from a unit to a service details and back/forth
  without issue.
- Verify that with a panel open, if you close the inspector the panel also
  closes.
- Verify that the inspector and panels work without the feature flag as
  expected.