When on the main menu, `/odoo?cids=1`, if you activate the debug assets,
the router will push a new key (debug) into the query string :
`/odoo?cids=1&debug=assets`. To fully activate the debug, a reload will
be done. After the reload, the action service will push the new loaded
state (the menu), taking into account the locked keys (in this case:
`cid` and `debug`), which will inverse the order of the query string :
`/odoo?debug=assets&cids=1`.

This occurs because, the order of the keys on the query string will
depend on: the push order; if the keys are locked keys or not; and of
the kind of push state (replacement or simple push state). The issue
with this almost "random" order of the keys, is that the router could
push the same URL (with keys in different order) multiple times into the
browser history.

Before this commit, to compare the actual URL with the new one, we just
compare the two strings, and if the order of the query strings are not
the same the URLs are considered as different.

This commit, will avoid this issue by deep comparing the query string as
objects, so when just a difference of order exists in the query string,
they will be considered as the same URL.

opw-3557575