Dashboard inaccessible after JS error

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.

Issue Description

When a JS error causes the dashboard to crash (white screen), the browser keeps redirecting you to the same page/filter that caused the crash and you have to clear the local storage (the brower_last_location key) to be able to navigate to another page.
Even if you go to the start page or a different class, it still redirects you back.

Steps to reproduce

1. Go to a collection with pointers
2. Set the filter to Unique on a pointer field and apply (same bug as in #2657 )
3. The dashboard gets a JS error TypeError: l.get is not a function and the screen turns white
4. Navigate to a different class
5. You get redirected back to the same page and the JS error causes it to crash again

Deleting browser_last_location in local storage allows you to navigate to a different page.

Actual Outcome

The browser keeps redirecting you to the page that causes the crash.

Expected Outcome

Don't redirect to the previous page on page load.

Environment

Dashboard

• Parse Dashboard version: 7.3.0-alpha.14
• Browser (Safari, Chrome, Firefox, Edge, etc.): Firefox
• Browser version: 140.0.4

Logs

TypeError: l.get is not a function at dashboard.bundle.js:2:2240738

Reproduce the crash in Firefox using a collection with pointers and the Unique filter, then inspect how the dashboard reads and writes the browser_last_location local-storage key during page loading. Done means a crash no longer traps the browser on the failing page and navigation to another class or the start page works without manually clearing storage.