Makes navigation hash and qs safe

Makes navigation hash and qs safe

This branch address two problems occuring in navigation

-onLogin is eating querystrings and hashes when a url with them is entered
into a location bar as part of the process of processing namespaces in the
url. To remedy this, we get the processed url, then add the querystring and
hash to it.
-_navigate in the routing extension wasn't hash aware. We copy the getQS
methods for hashes.

Looking at other commits in this area of the code, it looks like this is
regrettably untestable. (e.g. r667 touched this same part of onlogin and
pointed out we can't handle nav tests in test-prod). If the reviewer has
suggestions, I'm happy to pursue them.

https://code.launchpad.net/~jcsackett/juju-gui/why-do-the-querystrings-die-why-why/+merge/168153

(do not edit description out of merge proposal)

[j.c.sackett, 2013-06-07 19:19:08]

Please take a look.

[jeff.pihach, 2013-06-07 19:36:03]

LGTM to get you unblocked.

As per our hangout...
I feel that this is a bandaid over the real problem, that parse() and url()
aren't hash and query param safe. Could you please create a bug and a card in
our maintenance lane so that we can go in there and fix the real issue later.

[j.c.sackett, 2013-06-07 19:49:47]

On 2013/06/07 19:36:03, jeff.pihach wrote:
> LGTM to get you unblocked.
> 
> As per our hangout...
> I feel that this is a bandaid over the real problem, that parse() and url()
> aren't hash and query param safe. Could you please create a bug and a card in
> our maintenance lane so that we can go in there and fix the real issue later.

Bug and card have been created[1]; thanks for agreeing to this fix to unblock
other work.

[1]: https://bugs.launchpad.net/juju-gui/+bug/1188784

[j.c.sackett, 2013-06-07 19:54:10]

Please take a look.

[j.c.sackett, 2013-06-10 13:28:33]

On 2013/06/07 19:54:10, j.c.sackett wrote:
> Please take a look.

It's worth pointing out that Ben has handled the underlying problem here:
https://codereview.appspot.com/9830046/

I'll keep this up for now to track that, but if it's going to land soon then
there's no need for this to land, as his branch will unblock us.