Error State Feedback

- Logging out across tabs often produces a ` problem logging out` message. My gut tells me because once the first tab removes the user from `localStorage`, the rest of the tabs get a null.

- When the user session on the server has expired, but they aren't logged out on their client yet. This ends up with `403`s that are not handled great.

- When the current user is not an admin, but needs to be.

- Be more strict about error messages coming out of `quicklyAddToCollection()`, `removeCollectionEntry()`, `etc()`. Sometimes just simple UI failures trigger messages that server interaction did not happen successfully, even though it did.

- probably more. I'll add them as I encounter them.

Start by tracing the error handling around quicklyAddToCollection() and removeCollectionEntry(), then inspect the logout and 403 paths described in the issue. Confirm when server requests succeed versus when UI failures occur. Done means the listed session, authorization, and collection-operation cases produce accurate, useful feedback without falsely reporting failed server interactions.

Written by the indexing model from the issue text.