Pre-emptively trigger login after google token expired

[tyler-dane]

Feature Title

Pre-emptively trigger login after google token expired

Feature Description

Currently, the user's session might be active, but their google access token has expired. Compass doesn't know that the google access token expired, though, because it doesn't proactively check for it. Instead, it tries to make a normal event change request. Then google responds letting us know that the token expired, which we use to log the user out and redirect them to the sign in page.

The down side of this is that the user thought they were all good and spent time making/updating an event, only to be promptly redirected to login without any warning.

Instead, we should redirect the user before they're able to make any changes, providing a nice UX/message about why this is important.

Use Case

No response

Additional Context

implementation idea(s):

• use the WebSocket's connection as a trigger to run a preliminary check
• if a user returns the compass after a long time, the session with be refreshed. before/after that happens, do a preemptive GET request on a Google calendar resource. This will let us know if their access token is still valid. There's probably a better way to