Change the deploy button to Commit after deploy.
Defer fetching updates until first render; first step towards new update ux

Move upgrade-charm to be its own viewlet; unstyled first iteration

Make prep.
Merge pull request #401 from huwshimi/commit-deploy-label

Change the deploy button to Commit after deploy

The deploy button should change to "Commit" after the first deploy.

QA:
- drag a charm to the canvas
- the deploy button should have the label "Deploy"
- click Deploy and Confirm
- The button should now say "Commit"
Implement the create container workflow.

No matter how the user enters the workflow, they should end up seeing
the form to select a container type and (optionally) constraints.
Merge pull request #393 from kadams54/unit-constraints

Implement create container workflow

Adds support for creating different types of containers, including KVMs with constraints. Regardless of how you get into the workflow (dropping on a header drop target, using the header link, dropping on an existing container or machine), the full workflow should now occur, rather than the previous abbreviated one that assumed an LXC container.

## QA

With the `mv` flag. Test all the various entry points for creating a container:

1) Click on the "Add container" link. (Note: should this link be hidden when a machine is not selected?)
2) Drag and drop an unplaced service on the container header (when a machine is selected).
3) Drag and drop an unplaced service on an existing container (should add directly, no need for the create form).
4) Drag and drop an unplaced service on an existing machine (should bring up the create container form).
5) Click on the move icon for an unplaced service - try with both existing containers and new containers.

Aside from the above, just try to break things in various ways. Be sure to verify that any bugs found are not present on upcoming.jujucharms.com, as there are still a lot dragons to be slayed. For example, the container column is not great about updating if you have one machine selected and then drag and drop onto another machine.
Only allow one unit token to be in placement mode.
Tests rearranged to reflect new viewlet.
Merge pull request #404 from huwshimi/single-place

Only allow one unit token to be in placement mode

To prevent the list of machines and containers getting outdated by starting the move form on multiple unit tokens this branch makes it so you can only show the form on once token at once.

See: https://bugs.launchpad.net/juju-gui/+bug/1329224

QA:
- drag several charms to the canvas
- open the machine view
- click the 'move to' icon on one of the tokens
- now click on a different 'move to' icon
- the second token should now display the placement form and the first token should be reset to its initial state
- subsequent clicks on 'move to' icons should continue to only display the form on the last clicked token
Merge pull request #405 from makyo/cw-calls

Move update charm to new UX - first iteration

This branch moves the update charm functionality out of the service overview viewlet and into its own viewlet that can be loaded on demand, rather than on opening the inspector.  Note that there are follow-up style branches, and may be follow-up technical branches as well - first iteration.