Implement error notice infrastructure in admin settings and email reports subscription panel

## Feature Description


Implement these notice variants [PUE Errors - UX copy](https://docs.google.com/spreadsheets/d/1DEEPVKEtMklfHIIwyLR7MTwf8eEa_8dMBb_E8cuazgE/edit?gid=0#gid=0) in the user email reports subscription panel for admins only

---------------

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

## Acceptance criteria

* When all emails in the last batch have failed to send an Error Notice should be displayed in the Admin Settings within the Email reports section as well as in the email reports User settings side panel.
* The notices should be displayed when logged in as an Admin user only - view only users should not see this notice.
* Notices should only appear after all three send attempts for a batch fail and they should clear once a subsequent batch succeeds.

## Implementation Brief

* [x] Update `includes/Core/Email_Reporting/REST_Email_Reporting_Controller.php`
  * Add new `READABLE` route: `core/site/data/email-reporting-failure` 
    *  Compute data from `Email_Log_Batch_Query` (latest batch where all logs are `gsk_email_failed` after `MAX_ATTEMPTS`) and `META_ERROR_DETAILS` to extract the category (`wp_error` code). Clear it when a later batch has any `gsk_email_sent`.
  * Consider a central config (e.g., `includes/Core/Email_Reporting/Error_Notices_Map.php`) keyed by the error reason codes already logged (`network_error`, `permissions_revoked`, `property_deleted`, `server_error`, `scheduler_error`, `sending_error`, `other_error`), and mapped to their copy and CTA, etc, something like how we handle AdSense server notifications (`assets/js/hooks/useAdSenseNotifications.js`). 
    * `Error_Notices_Map` can expose one method to append content and other details within switch statement like we do in `Google\Site_Kit\Core\Authentication\Clients\OAuth_Client_Base::get_error_message()`

* [x] Datastore updates in `assets/js/googlesitekit/datastore/site/email-reporting.js`

  * Add selector/resolver `getEmailReportingFailure()` returning either `undefined` (loading), `null` (no terminal failure), or an object like `{ category: 'network_error', isTerminal: true, batchID, lastUpdated }`. If we do error data mapping on the backend via `Error_Notices_Map` include the content, CTA, etc to the response as well.
    * Resolver should invoke the new fetch store eq. `fetchGetEmailReportingFailureStore` that reads a new REST endpoint `core/site/data/email-reporting-failure`.
  * Optionally add a companion selector `hasEmailReportingFailure()` returning a boolean when `isTerminal && category`.

* [x] Add `assets/js/components/email-reporting/notices/EmailBatchErrorNotice.js`

  * Use `useSelect( CORE_SITE ).getEmailReportingFailure()` and `! viewOnly` to gate rendering.
  * Reuse an existing notice component pattern (e.g., structure of `AnalyticsDisconnectedNotice` or any banner in `assets/js/components/email-reporting/UserSettingsSelectionPanel/Notices.js`) as the starting point: a heading + body + optional CTAs.
  * Map `category` to copy/links via the PUE config, and render only when `failure && failure.isTerminal`
  * Keep it contained to `assets/js/components/email-reporting/UserSettingsSelectionPanel/Notices.js` so other panels stay unaffected.

* [x] Ensure the notice resets/clears when a batch succeeds (or no terminal failure is present).

### Test Coverage

* Update `tests/phpunit/integration/Core/User/REST_Email_Reporting_ControllerTest.php`
* Update `assets/js/googlesitekit/datastore/site/email-reporting.test.js` to include coverage for new resolver/selector

## QA Brief

* Copy-paste and run the following SQL into your site's database that mocks the logs generated after emails are sent.
<Details>
<Summary>SQL with all emails FAILED</Summary>

```
SET NAMES utf8mb4;

-- Insert posts and capture their IDs
INSERT INTO `wp_posts` (`post_author`, `post_date`, `post_date_gmt`, `post_content`, `post_title`, `post_excerpt`, `post_status`, `comment_status`, `ping_status`, `post_password`, `post_name`, `to_ping`, `pinged`, `post_modified`, `post_modified_gmt`, `post_content_filtered`, `post_parent`, `guid`, `menu_order`, `post_type`, `post_mime_type`, `comment_count`) VALUES
(1,	NOW(),	NOW(),	'',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76b',	'',	'gsk_email_failed',	'closed',	'closed',	'',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76b',	'',	'',	NOW(),	NOW(),	'',	0,	'https://sitekitssl.10uplabs.com/?post_type=gsk_email_log&#038;p=116',	0,	'gsk_email_log',	'',	0),
(2,	NOW(),	NOW(),	'',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76b',	'',	'gsk_email_failed',	'closed',	'closed',	'',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76b-2',	'',	'',	NOW(),	NOW(),	'',	0,	'https://sitekitssl.10uplabs.com/?post_type=gsk_email_log&#038;p=117',	0,	'gsk_email_log',	'',	0),
(3,	NOW(),	NOW(),	'',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76b',	'',	'gsk_email_failed',	'closed',	'closed',	'',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76b-3',	'',	'',	NOW(),	NOW(),	'',	0,	'https://sitekitssl.10uplabs.com/?post_type=gsk_email_log&#038;p=118',	0,	'gsk_email_log',	'',	0);

-- Get the auto-generated IDs for reference
SET @post_id_1 = LAST_INSERT_ID();
SET @post_id_2 = @post_id_1 + 1;
SET @post_id_3 = @post_id_1 + 2;

-- Insert postmeta using the captured IDs
INSERT INTO `wp_postmeta` (`post_id`, `meta_key`, `meta_value`) VALUES
(@post_id_1,	'_batch_id',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76b'),
(@post_id_1,	'_report_frequency',	'monthly'),
(@post_id_1,	'_report_reference_dates',	'{\"startDate\":1766361600,\"sendDate\":1768953600,\"compareStartDate\":1763769600,\"compareEndDate\":1766275200}'),
(@post_id_1,	'_send_attempts',	'3'),
(@post_id_1,	'_error_details',	'{\"errors\":{\"email_report_section_build_failed\":[\"title must be a non-empty string\"]},\"error_data\":[]}'),
(@post_id_2,	'_batch_id',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76b'),
(@post_id_2,	'_report_frequency',	'monthly'),
(@post_id_2,	'_report_reference_dates',	'{\"startDate\":1766361600,\"sendDate\":1768953600,\"compareStartDate\":1763769600,\"compareEndDate\":1766275200}'),
(@post_id_2,	'_send_attempts',	'3'),
(@post_id_2,	'_error_details',	'{\"errors\":{\"email_report_section_build_failed\":[\"title must be a non-empty string\"]},\"error_data\":[]}'),
(@post_id_3,	'_batch_id',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76b'),
(@post_id_3,	'_report_frequency',	'monthly'),
(@post_id_3,	'_report_reference_dates',	'{\"startDate\":1766361600,\"sendDate\":1768953600,\"compareStartDate\":1763769600,\"compareEndDate\":1766275200}'),
(@post_id_3,	'_send_attempts',	'3'),
(@post_id_3,	'_error_details',	'{\"errors\":{\"email_report_no_data\":[\"No email report data available.\"]},\"error_data\":[]}');
```

</Details>

* Download this [development version](https://fueled.slack.com/files/U02MMFPAXDW/F0A9P92UD1B/google-site-kit-tester.2.0.2.zip) of the tester plugin (in case the latest has still not got all Email Reporting features). Within "Email reporting", toggle the "Show Email Log Post Type". Save settings and refresh the page (your WP Admin). Then go to the "SK Email Logs" post link in the WP Admin Menu. This will show you all the email logs. Ensure there are 3 new records there that have been inserted by the SQL query above. All of them have "Failed" with errors.
* Now in the plugin, enable email reporting and test the side panel and admin settings. There should be an error message displayed in both places when email reporting is enabled. And no error should be displayed when it is disabled. Also test that only admins see the error message and it is not visible to view only users who open the side panel.
* Now simulate a simple run of new emails using [these bug bash instructions](https://docs.google.com/document/d/14ACA9OVRGUnRYpJD2U6kuxarcO2inuOOlRy3tctKm5s/edit?tab=t.0#heading=h.5n2hhosy3wku). Check that emails were sent correctly after about 1 minute and the errors in both areas should automatically clear. If you aren't able to send emails, run the following SQL that will mock a new email batch where one email was successful and two the failed. In this case, since not all emails have failed, there should be no error displayed.

<Details>
<Summary>SQL with 2/3 emails FAILED</Summary>

```
SET NAMES utf8mb4;

-- Insert posts and capture their IDs
INSERT INTO `wp_posts` (`post_author`, `post_date`, `post_date_gmt`, `post_content`, `post_title`, `post_excerpt`, `post_status`, `comment_status`, `ping_status`, `post_password`, `post_name`, `to_ping`, `pinged`, `post_modified`, `post_modified_gmt`, `post_content_filtered`, `post_parent`, `guid`, `menu_order`, `post_type`, `post_mime_type`, `comment_count`) VALUES
(1,	NOW(),	NOW(),	'',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76c',	'',	'gsk_email_sent',	'closed',	'closed',	'',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76c',	'',	'',	NOW(),	NOW(),	'',	0,	'https://sitekitssl.10uplabs.com/?post_type=gsk_email_log&#038;p=116',	0,	'gsk_email_log',	'',	0),
(2,	NOW(),	NOW(),	'',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76c',	'',	'gsk_email_failed',	'closed',	'closed',	'',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76c-2',	'',	'',	NOW(),	NOW(),	'',	0,	'https://sitekitssl.10uplabs.com/?post_type=gsk_email_log&#038;p=117',	0,	'gsk_email_log',	'',	0),
(3,	NOW(),	NOW(),	'',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76c',	'',	'gsk_email_failed',	'closed',	'closed',	'',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76c-3',	'',	'',	NOW(),	NOW(),	'',	0,	'https://sitekitssl.10uplabs.com/?post_type=gsk_email_log&#038;p=118',	0,	'gsk_email_log',	'',	0);

-- Get the auto-generated IDs for reference
SET @post_id_1 = LAST_INSERT_ID();
SET @post_id_2 = @post_id_1 + 1;
SET @post_id_3 = @post_id_1 + 2;

-- Insert postmeta using the captured IDs
INSERT INTO `wp_postmeta` (`post_id`, `meta_key`, `meta_value`) VALUES
(@post_id_1,	'_batch_id',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76c'),
(@post_id_1,	'_report_frequency',	'monthly'),
(@post_id_1,	'_report_reference_dates',	'{\"startDate\":1766361600,\"sendDate\":1768953600,\"compareStartDate\":1763769600,\"compareEndDate\":1766275200}'),
(@post_id_1,	'_send_attempts',	'1'),
(@post_id_2,	'_batch_id',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76c'),
(@post_id_2,	'_report_frequency',	'monthly'),
(@post_id_2,	'_report_reference_dates',	'{\"startDate\":1766361600,\"sendDate\":1768953600,\"compareStartDate\":1763769600,\"compareEndDate\":1766275200}'),
(@post_id_2,	'_send_attempts',	'3'),
(@post_id_2,	'_error_details',	'{\"errors\":{\"email_report_section_build_failed\":[\"title must be a non-empty string\"]},\"error_data\":[]}'),
(@post_id_3,	'_batch_id',	'f1a73c27-4481-4e0b-bc98-b90eb2cbe76c'),
(@post_id_3,	'_report_frequency',	'monthly'),
(@post_id_3,	'_report_reference_dates',	'{\"startDate\":1766361600,\"sendDate\":1768953600,\"compareStartDate\":1763769600,\"compareEndDate\":1766275200}'),
(@post_id_3,	'_send_attempts',	'3'),
(@post_id_3,	'_error_details',	'{\"errors\":{\"email_report_no_data\":[\"No email report data available.\"]},\"error_data\":[]}');
```

</Details>

## Changelog entry

* Implement error notice infrastructure in admin settings and email reports subscription panel.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Implement error notice infrastructure in admin settings and email reports subscription panel #11860

Feature Description

Acceptance criteria

Implementation Brief

Test Coverage

QA Brief

Changelog entry

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Implement error notice infrastructure in admin settings and email reports subscription panel #11860

Description

Feature Description

Acceptance criteria

Implementation Brief

Test Coverage

QA Brief

Changelog entry

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions