Routing: New useLocation() features are still unused and (manually) implemented incorrectly in some instances

[Danziger]

The navigate() function (from useLocation()) can be called with 3 special values:

• navigate("prev")
• navigate("next")
• navigate("up")
• navigate(number)

Additionally, useLocation() also returns a back() functions.

There are multiple instances where these new capabilities can be used:

• Review instances where the "back" arrow has a hardcoded value instead of actually going back (or up).
• Some routes such as /notifications or /transactions use a ?back=<path> param that can probably be removed and replace with a simpe call to back(), or a simpler boolean param (e.g. ?goesBack=1|0). There's a comment about this on the back button click handler in ArConnect/src/routes/popup/transaction/[id].tsx.
• The new navigate() function (from useLocation()) includes an option.search param to add search params to the URL, but some usages of navigate() still append it manually to the first param (make sure you tackle this issue after the previous one, as that's where most search params are being used).