Ignore in-flight ac suggestions on submit.

- See #1237457

If you hit submit while there's an ongoing ajax request for completion
suggestions the timing can be that you get suggestions overlaying your real
results

This adds a simple flag 'off' that is used to track if we should ignore those
in flight suggestions when they come back.

QA:

Compare the results of the test from the bug on comingsoon vs this branch.
When you hit enter quickly after the 'i' in wiki you should not get the
results popup while you do on comingsoon.
For IE, manually trigger focus handler.

- The YUI simulate event is not triggering the focus handler in IE.
Merge pull request #84 from mitechie/quick-search-behave

- See #1237457

If you hit submit while there's an ongoing ajax request for completion
suggestions the timing can be that you get suggestions overlaying your real
results

This adds a simple flag 'off' that is used to track if we should ignore those
in flight suggestions when they come back.

QA:

Compare the results of the test from the bug on comingsoon vs this branch.
When you hit enter quickly after the 'i' in wiki you should not get the
results popup while you do on comingsoon.
Notify in the inspector when a service is dying.
Merge pull request #85 from frankban/dying-service

QA:
Test the functionality in a sandbox GUI instance:
  - `make devel`;
  - deploy a service;
  - open the inspector for that service;
  - open the JavaScript console and run:
    `app.db.services.item(0).set('life', 'dying');`
  - you should see the "service is being destroyed" message
    in the inspector.

Test the functionality in a real Juju environment.
  - bootstrap an environment and deploy the gui (e.g. with juju-quickstart);
  - run `juju set juju-gui juju-gui-source="https://github.com/frankban/juju-gui.git dying-service"` 
    and wait some minutes for the new release to be built: 
    you can observe the progress with `juju debug-log` or running
    `tailf ~/.juju/local/log/unit-juju-gui-0.log` if you are using a local env;
  - deploy a service;
  - open the inspector for that service;
  - destroy the service, either by using the inspector "destroy" button or
    the cli command;
  - you should see the "service is being destroyed" message
    in the inspector.