Sync cloud integration on Authorization problems

[sergeibbb]

Description

Here we sync the cloud connected integration with GKDev when we face an authorization problem hoping that during the sync they respond us with the actual token.

If we see that we keep facing the same error we don't try to sync again. Instead we disconnect the integration soon letting user know that they need to take an action to reconnect.

Related to:

• #4297
• #4192

Follow-ups:

• [ ] we'll need to create an issue to improve connecting failed cloud integrations back. Now it reconnects on "Sync" clicking, but it ignores click on the "socket plug" in the Remotes list.

Checklist

• [x] I have followed the guidelines in the Contributing document
• [x] My changes follow the coding style of this project
• [x] My changes build without any errors or warnings
• [x] My changes have been formatted and linted
• [ ] My changes include any required corresponding changes to the documentation (including CHANGELOG.md and README.md)
• [x] My changes have been rebased and squashed to the minimal number (typically 1) of relevant commits
• [x] My changes have a descriptive commit message with a short title, including a Fixes $XXX - or Closes #XXX - prefix to auto-close the issue that your PR addresses