Navigating to accessible dandiset after failed dandiset load causes errors in GUI

[jjnesbitt]

It appears that when using the client, if the access of a dandiset fails for any reason (doesn't exist, embargoed without access, version string is wrong, etc.), then immediately navigating to a dandiset which is accessible through the "public dandisets" page fails and raises a bunch of errors. This is seemingly due to carried over state, and its interaction with the meditor. Steps to reproduce:

1. Navigate to a bogus dandiset URL (https://dandiarchive.org/dandiset/123456/blahblahblah)
2. Click on "Public Dandisets"
3. Click any listed dandiset
4. Observe errors

The reason I say it's connected to the meditor is because I observed the following console error:

Cannot destructure property 'modelValid' of 'editorInterface.value' as it is null

[waxlamp]

Seems to be the same class of problem as reported in #2081.