Handle case where stored refresh token expires

[pkalita-lbl]

When a user logs in a refresh token is generated for the user and the app stores it in persistent storage. The refresh token used to issue new shorter-lived access tokens. But the refresh token itself will expire after 365 days (by default -- it is configurable per nmdc-server environment). When the app detects that the refresh token has expired (as evidenced by an exchange for a new access token failing), the app needs to revert to a logged-out state and the user will need to log in again.