site-kit-wp: Add "Retry" button to regular JS error notices in the plugin

Follow-up to #5236: In addition to the ReportErrors, a retry button should also be added to similar JS-based errors that appear outside of Site Kit widgets - specifically in module setup flows and module settings.

---

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

• The ErrorNotice component (primarily used throughout setup flows and module settings) should also display a “Retry” button if the provided error comes with the necessary selectorData defined on it.
• The logic for whether to display the “Retry” button or not should be similar to #5236.
• When the user clicks the button, the corresponding store selector should also be invalidated.

Implementation Brief

• In the ErrorNotice component, when an error has a selectorData argument: render a Button component with the following:
  • Children should be __( 'Retry' ).
  • Define a callback function for the retry handler which dispatches the invalidateResolution action like in #5236/https://github.com/google/site-kit-wp/blob/741869a1aeef844d01d946de37a9d1af60d699f8/assets/js/components/ReportError.js#L132-L140.
  • Pass the above callback function to the Button component’s onClick prop.
• It would be worth extracting at least the logic for what errors are considered “retry-able” from https://github.com/google/site-kit-wp/blob/741869a1aeef844d01d946de37a9d1af60d699f8/assets/js/components/ReportError.js#L122-L128 into a shared function used between both ErrorNotice and ReportError. Any other code/logic that can be shared as well, should be.

Test Coverage

• Add tests to ensure the error notice renders/doesn’t render the button and runs the callback based on the error passed to it.

QA Brief

• An example of a retryable ErrorNotice can be found in the Tag Manager setup page.
• Using Tweak:
  • Set up a rule for the URL http://sitekit.10uplabs.com/wp-json/google-site-kit/v1/modules/tagmanager/data/accounts?_locale=user, substituting your protocol://host as needs be.
  • Set the status code to be an error e.g. 403.
  • Set the response payload to something like this:

{
  "code": "foo",
  "message": "Mock error fetching tagmanager accounts!",
  "data": {}
}

• Start the Tab Manager setup flow.
• On the first page of it, the error should appear with a Retry button.
• Disable the Tweak rule and press retry, the error should resolve.

Changelog entry

• Add a “Retry” button for most errors in the plugin, except for some auth and other select errors.