Validate locally stored tokens for Cloud Integrations

[axosoft-ramint]

Our "sync cloud integrations" process checks if integrations were disconnected in the backend and disconnects them locally if they were, but it doesn't check if the active token has changed on the backend. In this case, it should update its local token.

This can be done in several ways:

1. During the passive sync that runs during checkin, grab the actual token for each connected one, then validate against what you have stored locally and updated if needed.
2. (Preferred): When using a cloud token, if you get an error, or when it expires, try calling the /refresh backend route first to refresh the token, and give the call another try. If it still fails after refresh, show an error.

Note for 2 that when calling the refresh route, if the token on the backend differs than what you sent it in the body, it returns the new token instead of the current one.