When using AnythingLLM with a password or multi-user auth state the default token expiry is set to 30 days expiration (TBD custom config for this value).

If you are logged in and do not re-visit the system for some time where the token then expires on revisit the token will fail to verify and will return a null value, which will fatally crash the bcrypt compareHash function. Passing an empty '' instead when invalid will then cause an infinite re-render on the login screen.

Additional work was required to have this work when the session is fully expired:

• Invalidate token as normal
• Send the user to log in, but prevent auto login via a query param set during redirect due to invalid auth.
• User can log in again and get a new session token.

• Tested as all roles in multi-user
• Tested with just password
• Tested with no password instance

resolves #947