Adds alert center redux store

[vraja-pro]

Context

Summary

This PR can be summarized in the following changelog entry:

• Adds alert center to dashboard redux store.

Relevant technical choices:

• I added a method to get the message from the notification object for the paragraphs.

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

• Go to Yoast SEO -> General page and check you notifications and problems. ( You can trigger notification by adding new content types and resetting the indexables in the yoast test helper, you can trigger problems by disabling Search engine visibility in the Settings->Reading)
• Add the following line in wp-config.php or snippets plugin:

define( 'YOAST_SEO_NEW_DASHBOARD_UI', true );

• Go to Yoast SEO -> General page
• Check you see the same problems and notifications.
• Check the number in the title of the problems and notifications matched the number of active alerts.
• Hide notifications and check the number has changed in the title, the notification has moved to the hidden Collapsible and the hidden Collapsible has the right number of hidden notifications.
• Hide more than one notification and check the translation has changed to plural (e.g. hidden notifications, hidden problems) in the Collapsible.
• Restore notifications and problems from the hidden Collapsible and check the Collapsible disappears.
• Hide only one notification/problem and check the label is singular (e.g hidden problem, hidden notification.
• Hide all notification and check a text appears under the title: "No new notifications."
• Refresh and check changes were saved.

Relevant test scenarios

• Changes should be tested with the browser console open
• Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
• Changes should be tested on different editors (Default Block/Gutenberg/Classic/Elementor/other)
• Changes should be tested on different browsers
• Changes should be tested on multisite

Test instructions for QA when the code is in the RC

• QA should use the same steps as above.

QA can test this PR by following these steps:

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

UI changes

• This PR changes the UI in the plugin. I have added the 'UI change' label to this PR.

Other environments

• This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.

Documentation

• I have written documentation for this change. For example, comments in the Relevant technical choices, comments in the code, documentation on Confluence / shared Google Drive / Yoast developer portal, or other.

Quality assurance

• I have tested this code to the best of my abilities.
• During testing, I had activated all plugins that Yoast SEO provides integrations for.
• I have added unit tests to verify the code works as intended.
• If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
• I have written this PR in accordance with my team's definition of done.
• I have checked that the base branch is correctly set.

Innovation

• No innovation project is applicable for this PR.
• This PR falls under an innovation project. I have attached the innovation label.
• I have added my hours to the WBSO document.

Fixes Add Notifications to Alert center

[coveralls]

Pull Request Test Coverage Report for Build d2aa0ec4ff7ec63ba5b6c5cb96cc410a3fa28b67

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 1 of 52 (1.92%) changed or added relevant lines in 7 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+5.2%) to 54.475%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
admin/class-yoast-notification.php	0	2	0.0%
packages/js/src/dashboard/components/notifications.js	0	2	0.0%
packages/js/src/dashboard/components/problems.js	0	4	0.0%
src/helpers/notification-helper.php	0	6	0.0%
packages/js/src/dashboard/components/alerts-list.js	0	9	0.0%
packages/js/src/dashboard/store/alert-center.js	0	28	0.0%

Files with Coverage Reduction	New Missed Lines	%
packages/js/src/dashboard/components/notifications.js	1	0.0%

Totals
Change from base Build 9df74654c5e7c4056b63d95a59e204a300afd402:	5.2%
Covered Lines:	29533
Relevant Lines:	54476

---

💛 - Coveralls

[igorschoester]

CR 🏗️

[igorschoester]

No toggle status or error support?

[vraja-pro]

I think its something to ask UX what we want to do for error or request status?

[igorschoester]

CR ❓
Really liking the refactor to not pre-group 😄
I commented some more. Besides maybe the tests these are just that, comments. Feel free to leave them or address the tests in a follow-up?

[igorschoester]

If we ever run into encoding issues, we could try to switch this to FormData

[igorschoester]

You could write tests for these?

[vraja-pro]

I added tests for the new components
I added tests for the store but it was difficult to test the happy path with the toggleAlert with regular js object for a state.

[pls78]

CR && Acc: ✅