Fixes routing issues around search and charm tabs

Fixes routing issues around search and charm tabs

- See bug #1205468
- See bug #1200743

Summary
-------
There are two problems. The first is that when doing some view state changes
we need to also clear the hash so that it doesn't carry around. We also clear
the charm id when doing searches in fullscreen mode. This helps the browser
app ack that there were changes in state and show the correct view.

The second issue was that clicking a tab on the fullscreen charm details after
a search causes two #bws-readme (for instance) to be added. One is before the
query string and one is after the querysting. This is caused by our double
dispatch and the fact that our routing code builds urls with query strings
after the hash of the url. This is not proper. The Y.App adds it to the end of
the url. In this way we ended up with it in both places.

Our routing code would then assume the whole #bws-readme?text=apache2 was the
hash of the url and that there was no query string. All kinds of trouble came
out of this.

Tests are added to verify the changes work as expected given our sample bad
urls.

QA
---
To QA simpler go through the steps in the two bugs and it should work as
expected. Other QA would be to verify that other usage is not adversely
effected by moving the hash to be at the end of the url while the querystring
is immediately after the path.

https://code.launchpad.net/~rharding/juju-gui/routing-issues/+merge/177401

(do not edit description out of merge proposal)

[rharding, 2013-07-29 16:00:11]

Please take a look.

[j.c.sackett, 2013-07-29 16:29:14]

LGTM, thanks.

https://codereview.appspot.com/12036043/diff/1/app/assets/javascripts/ns-rout...
File app/assets/javascripts/ns-routing-app-extension.js (right):

https://codereview.appspot.com/12036043/diff/1/app/assets/javascripts/ns-rout...
app/assets/javascripts/ns-routing-app-extension.js:104: var hashIndex =
qs.indexOf('#');
Thanks for using hashIndex instead of hashIdx. Deryck is, I'm sure, proud.

[jeff.pihach, 2013-07-29 16:54:49]

QA No Go

Go to http://localhost:8888/fullscreen/precise/cinder-8/
Click, Readme, Interfaces
Click JuJu (top left)
Click Browse
Url will now be http://localhost:8888/fullscree/##bws-interfaces

Can't repro on jujucharms.com because I can't get past the readme step, so I'm
not sure if this was pre-existing or a side effect of this branch.

[rharding, 2013-07-29 17:54:17]

Please take a look.

[rharding, 2013-07-29 18:10:57]

Please take a look.

[jeff.pihach, 2013-07-29 19:33:24]

LGTM Thanks for getting these blockers/criticals fixed!
QA OK

This branch exposed an issue where the router is not dispatching when the hash
changes. https://bugs.launchpad.net/juju-gui/+bug/1206239

[rharding, 2013-07-29 19:39:46]

*** Submitted:

Fixes routing issues around search and charm tabs

- See bug #1205468
- See bug #1200743

Summary
-------
There are two problems. The first is that when doing some view state changes
we need to also clear the hash so that it doesn't carry around. We also clear
the charm id when doing searches in fullscreen mode. This helps the browser
app ack that there were changes in state and show the correct view.

The second issue was that clicking a tab on the fullscreen charm details after
a search causes two #bws-readme (for instance) to be added. One is before the
query string and one is after the querysting. This is caused by our double
dispatch and the fact that our routing code builds urls with query strings
after the hash of the url. This is not proper. The Y.App adds it to the end of
the url. In this way we ended up with it in both places.

Our routing code would then assume the whole #bws-readme?text=apache2 was the
hash of the url and that there was no query string. All kinds of trouble came
out of this.

Tests are added to verify the changes work as expected given our sample bad
urls.

QA
---
To QA simpler go through the steps in the two bugs and it should work as
expected. Other QA would be to verify that other usage is not adversely
effected by moving the hash to be at the end of the url while the querystring
is immediately after the path.

R=j.c.sackett, jeff.pihach
CC=
https://codereview.appspot.com/12036043