Fixed drag and drop of unplaced units.
Driveby to remove sidebar flash
Implemented non-drag-and-drop unit placing workflow.
Moved the search widget instantiaion and rendering into the charmbrowser view
Made loading indicator render in the proper place
Created search widget management extension to be mixed into the charmbrowser view
Search widget now functions properly being 100% rendered and managed in charmbrowser view
Merge branch 'fix-drop-unit' into fix-drop-unit-landing
Merge pull request #350 from makyo/driveby-flash

Quick driveby to remove the flash of charmbrowser introduced by the previous branch, just a matter of ordering.
Merge pull request #351 from huwshimi/fix-drop-unit-landing

Drag and drop of unplaced units was broken. This fixes it.

Bug: https://bugs.launchpad.net/juju-gui/+bug/1323199

QA:

drag a service to the canvas
open the machine view
drag the unplaced unit to 'create a machine'
open the javascript console and check there are no errors.
click deploy and confirm The unit should be on a new machine. Adding more units and dropping them on existing containers should work as well.
Merge pull request #341 from huwshimi/unit-placement-workflow

This is the click-through unit placement workflow.

Question: can we use constraints for creating machines/containers? If so I need to add that, if not I can remove that for now.

QA:
Use il and mv flags.
- Drag a service to the canvas. Click Deploy and Confim.
- Drag a different service to the canvas. Do not deploy.
- Open the machine view.
- In the "Unplaced units" column there should be one unit. Click the icon on the right hand side.
- A select box should appear and you should now be able to follow through with adding to a machine/container, creating new machines/containers etc. All the paths should work.
Fix height scaling issue with the inspectors
Added new tests for the search widget rendering functionality and fixed other failings.
Ensure charmbrowser is fully removed on destroy.
Do not re-render MV if already exists.
Merge pull request #354 from kadams54/charmbrowser-rerender

### QA

With the `il` flag.

1. Drag a service to the canvas
2. Click on the service and open the inspector
3. Close the inspector
4. Inspect the HTML of the sidebar

You should only see one set of charmbrowser HTML. You should **not** see anything like this:

    <div id="yui_3_11_0_1_1401404489618_1020" ...
        <div class="search-widget"...
        <div class="charm-list"...
    <div id="yui_3_11_0_1_1401404489618_1020" ...
        <div class="search-widget"...
        <div class="charm-list"...
Merge pull request #352 from kadams54/only-one-mv

### QA

1. Switch to machine view.
2. Use the inspector to view bundle details for a bundle and then click on the button in the details panel to deploy it.
3. You should only see one copy of each machine show up in the machines column. One machine 0, one machine 1. Not three of each.

Do some other playing around, switching between the canvas and MV (i.e., destroying MV, recreating it), etc. Make sure everything looks good.
Merge pull request #353 from hatched/search-widget-consolidated

This branch moves the search widget into the consolidated charmbrowser view. 

#### Note
After this branch lands you will be REQUIRED to use the `il` flag until it's completely removed as some changes in this branch were too much work to implement just to keep the flag working for a few more days.

#### To QA
Use the `il` flags
This branch moves the search widget so do a deep exploratory QA with the search widget and charmbrowser code.