Use simplified URLs for promulgated bundles.

Avoid showing the user part in the bundle URLs
displayed in the bundle browser view header and
in quickstart instructions.

Also moved the bundle location above the deployment
stats in the header, so that the URL is not hidden
by the "Deploy this bundle" button.

QA:
- make devel/debug/prod;
- search for bundles and pick a promulgated one;
- check the simplified bundle URL is showed in the header
  and in the quickstart howto (Deploy tab);
- now pick a non-promulgated bundle: this time the user
  is properly included in the URL.
Merge pull request #187 from frankban/promulgated-bundles

Avoid showing the user part in the bundle URLs
displayed in the bundle browser view header and
in quickstart instructions.

Also moved the bundle location above the deployment
stats in the header, so that the URL is not hidden
by the "Deploy this bundle" button.

QA:
- make devel/debug/prod;
- search for bundles and pick a promulgated one;
- check the simplified bundle URL is showed in the header
  and in the quickstart howto (Deploy tab);
- now pick a non-promulgated bundle: this time the user
  is properly included in the URL.
Handle peer relation for missing services.

    QA:
    - juju-quickstart the GUI in a local env;
    - juju set juju-gui juju-gui-console-enabled=true
    - deploy wordpress from the JS console:
      app.env.deploy('cs:precise/wordpress-21', 'wordpress', null, null, 1, null);
      You should see a "Relation added without matching service" error;
    - destroy the wordpress service using the GUI inspector;
    - now switch to this branch:
      juju set juju-gui juju-gui-source="https://github.com/frankban/juju-gui.git reorder-delta";
    - wait for the GUI to be ready again, this takes a while;
    - reload the GUI (CTRL-SHIFT-R);
    - deploy wordpress from the JS console:
      app.env.deploy('cs:precise/wordpress-21', 'wordpress', null, null, 1, null);
      You should see a "relation change wordpress:loadbalancer delayed"
      log message, and the wordpress relation tab should show the peer relation;
    - done, destroy your environment, thank you!
Merge pull request #186 from frankban/reorder-delta

QA:
- juju-quickstart the GUI in a local env;
- juju set juju-gui juju-gui-console-enabled=true
- deploy wordpress from the JS console:
  app.env.deploy('cs:precise/wordpress-21', 'wordpress', null, null, 1, null);
  You should see a "Relation added without matching service" error;
- destroy the wordpress service using the GUI inspector;
- now switch to this branch:
  juju set juju-gui juju-gui-source="https://github.com/frankban/juju-gui.git reorder-delta";
- wait for the GUI to be ready again, this takes a while;
- reload the GUI (CTRL-SHIFT-R);
- deploy wordpress from the JS console:
  app.env.deploy('cs:precise/wordpress-21', 'wordpress', null, null, 1, null);
  You should see a "relation change wordpress:loadbalancer delayed"
  log message, and the wordpress relation tab should show the peer relation;
- done, destroy your environment, thank you!
Bug #1269381 - Clarify keyboard shortcut help.

The shortcut labels had to match the lowercase version of the key. In
some cases that didn't make as much sense as the uppercase version. For
example, Shift+/ brings up the help, but Shift+? (the uppercase version)
is more intuitive. Add a way to separate the label displayed from the
actual keybinding (which had to be the lowercase version).
Merge pull request #189 from kadams54/1269381

The shortcut labels had to match the lowercase version of the key. In
some cases that didn't make as much sense as the uppercase version. For
example, Shift+/ brings up the help, but Shift+? (the uppercase version)
is more intuitive. Add a way to separate the label displayed from the
actual keybinding (which had to be the lowercase version).
Adds basic UI component for the Deployer Bar.
Merge pull request #185 from huwshimi/deployer-bar-view

Deployer bar view