[ADVAPP-32] & [ADVAPP-35] Ensure handling of invalid refresh_token for Outlook and Google

[Orrison]

Ticket(s) or GitHub Issue

• https://canyongbs.atlassian.net/browse/ADVAPP-35
• https://canyongbs.atlassian.net/browse/ADVAPP-32

Technical Description

If the refresh token fails to renew the access token by being invalid we inform the User and give them a flow to reconnect.

We will now also refresh refresh_tokens to make sure they are never stale.

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Content or styling update (Changes which don't affect functionality)
• DevOps
• Documentation

Screenshots (if appropriate)

Any deployment steps required?

A deployment step could be a command that needs to be executed or an ENV key that needs to be added, for example.

• Yes, please specify
• No

---

Before contributing and submitting this PR, make sure you have:

• Read the contributing guidelines.
• Title the PR with the ticket/issue number and a short description of the changes made. Or if no ticket/issue exists, title the PR with a short description of the changes made
• Linked a relevant ticket or issue or describe the issue/feature which this PR resolves/implements.
• Resolved all conflicts, if any.
• Rebased your branch PR on top of the latest upstream develop branch.