Fix unlock cancel flow

[rileystephens28]

Bug Description

When a user navigates to the send page while the keyring is in a locked state, the cancel flow does not work. Clicking the cancel button on the unlock screen attempts to navigate the user back to the send page, which then automatically redirects back to the unlock page. This results in a user being stuck on the unlock page until the correct password is entered.

Solution

When cancel button is clicked, find the last visited eligible path to navigate back to where an eligible path is defined as any path that does not automatically redirect to the unlock page. As of now the only ineligible paths are /send and /keyring/unlock.

[jdowning100]

Looks good to me. Does the linter automatically run? If not, can we have it automatically run after the file is saved, or a commit is added? This would be easier than having to manually run it.

[rileystephens28]

Linting is configured in pre-commit, github build.yml and can be manually run using one of the eight scripts declared in package.json. I will to double check that the prettier/eslint configs are universal for all these methods of linting in a future PR.