Include content policy state in RRM setup success notification GA events.

[techanvil]

Summary

Addresses issue:

• Update RRM Setup Success Notification GA Events to Include Content Policy State #12104

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 835f284 have been deleted.

[nfmohit]

This looks great, thanks @techanvil!

I've just left one comment for your consideration.

[nfmohit]

Shouldn't these tests be nested under GA event tracking? Also, I think we may be able to combine both test cases into one. WDYT?

[techanvil]

Thanks Nahid - they should be under GA event tracking. Re. combining the tests - I did start off taking that approach, but the amount of conditionality in the tests made me decide to separate them.

However, I've taken another look and refactored them to combine, and I think it's OK. Please see what you think.

[nfmohit]

LGTM, thank you @techanvil!