Enhancement/#12245 - Show RRM extreme policy violation in success setup notification

[hussain-t]

Summary

Addresses issue:

• Change notification for extreme policy violation when setting up RRM module #12245

Relevant technical choices

PR Author Checklist

• My code is tested and passes existing unit tests.
• My code has an appropriate set of unit tests which all pass.
• My code is backward-compatible with WordPress 5.2 and PHP 7.4.
• My code follows the WordPress coding standards.
• My code has proper inline documentation.
• I have added a QA Brief on the issue linked above.
• I have signed the Contributor License Agreement (see https://cla.developers.google.com/).

---

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

Code Reviewer Checklist

• Run the code.
• Ensure the acceptance criteria are satisfied.
• Reassess the implementation with the IB.
• Ensure no unrelated changes are included.
• Ensure CI checks pass.
• Check Storybook where applicable.
• Ensure there is a QA Brief.
• Ensure there are no unexpected significant changes to file sizes.

Merge Reviewer Checklist

• Ensure the PR has the correct target branch.
• Double-check that the PR is okay to be merged.
• Ensure the corresponding issue has a ZenHub release assigned.
• Add a changelog message to the issue.

[github-actions]

Storybook is ready:

• View Storybook

[github-actions]

Build files for 4bdf61f have been deleted.

[nfmohit]

Thanks for your work on this, @hussain-t!

I've left some minor feedback. As we're under some time constraints, I'll go ahead and address them myself. I hope that is okay.

Thanks again!

[nfmohit]

LGTM ✅

Note: I've verified that the failing E2E tests in CI are unrelated to the changes in this PR.