Once Jetpack authorization is invalidated, it may continue to stuck on the Settings page

[eason9487]

Describe the bug:

Once Jetpack authorization is invalid, it may continue to stuck on the settings page.

Kapture.2023-06-02.at.16.26.45.mp4

Steps to reproduce:

1. Make a Jetpack connected and authorized site temporarily inaccessible

2. Go to https://cloud.jetpack.com/ and select the site. Wait for a while. Reconnect Jetpack -> Disconnect Jetpack

   Kapture.2023-06-02.at.16.20.51.mp4

3. Go back to a GLA admin page.

4. GLA redirects to the Settings page and is continuously stuck in loading status.

Expected behavior:

GLA should redirect to the Jetpack (WordPress.com) reconnection page.

Actual behavior:

Users are unable to reconnect their sites with Jetpack.

Additional details:

This probably only happens when the authorization is invalidated from Jetpack side. Disconnecting from GLA won't fall into this issue.

Related codes:

• Set Jeppack connected flag to false when getting 401 from WCS
• jetpack/connected API doesn't check the above flag, so the active value in API response is still 'yes'
• Redirect to the corresponding reconnection page when getting 401
• Redirect to the Setting page when active is 'yes'