feat: $location.seach() should support semicolon (`;`) as an alternative delimiter to (ampersand) `&`

[IgorMinar]

per RFC $location should parse both of these as equivalent

https://myapp/some/path/?show=all&ascending=true&sortField=id
https://myapp/some/path/?show=all;ascending=true;sortField=id

since we also need to be able to serialize the params with some separator, we should make the separator configurable (with & being the default)

[caitp]

What happens if you have a URL like https://myapp/some/path/?show=all&ascending=true;sortField=id ? Looking at the recommendation, it looks like this could cause problems when entity references are used. Seems like you'd have to have some way of figuring out which delimiter is correct, in the case that they're both used.

I've written a naive implementation which just splits by both & and ;, but as stated, I see some problems with that approach.

I guess hopefully, you don't end up with weird urls like that

[Rob89]

Some APIs use semicolons within a QS parameter. e.g. stackexchange uses semicolons to seperate tags: http://api.stackexchange.com/2.1/search?order=desc&sort=activity&tagged=c%23;javascript&site=stackoverflow