feat: campaigns listeners for the data events api

[leogermani]

All Submissions:

• Have you followed the Newspack Contributing guideline?
• Does your code follow the WordPress' coding standards and VIP Go coding standards?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes proposed in this Pull Request:

This PR adds new events to the Data Events API to track interaction with Campaigns on the back-end.

In order to track the "lifecycle" of a campaign, we trigger a series of the same event, called "campaign_interaction", with action values for each state. It can be

• rendered: for when the campaign is rendered in the page (not necessarily seen by the user)
• form_submission: for when there's a submission to a form inside a popup. We are adding a newspack_popup_id to forms inside a popup to be able to identify it. We'll need to handle all forms we need to to track in this way. This PR does it for the Registration and Newsletter Subscription blocks.
• form_submission_success: for when the form submission returns success
• form_submission_failure: for when the form submission fails

How to test the changes in this Pull Request:

1. Checkout this PR. Checkout feat: add popups ids to forms in prompts newspack-popups#1057 in the popups plugin, and feat: add support to campaigns data event listeners newspack-newsletters#1087 in the newsletters plugin
2. Create a prompt that displays the Registration block and make it appear on your site
3. Add this snippet to your site:

Data_Events::register_handler( 'debug_popups_events', 'campaign_interaction' );

function debug_popups_events( $timestamp, $data, $user_id ) {
	error_log( print_r( $data, true ) );
}

4. Watch the error log
5. Load a page where the prompt will be displayed
6. Register through the prompt
7. Confirm registration works
8. Check your log after all the handlers are executed (you might need to refresh the page a couple of times, or you can go to Tools > Action Scheduler and manually run the campaign_interaction events)
9. In your log, you should be able to find this sequence:

[21-Feb-2023 14:05:11 UTC] [NEWSPACK-DATA-EVENTS][Newspack\Data_Events::handle]: Executing action handlers for "campaign_interaction".
[21-Feb-2023 14:05:11 UTC] Array
(
    [title] => Registration Overlay
    [frequency] => always
    [placement] => center
    [has_registration_block] => 1
    [has_donation_block] => 
    [has_newsletter_block] =>
    [action] => rendered
)

[21-Feb-2023 14:05:57 UTC] [NEWSPACK-DATA-EVENTS][Newspack\Data_Events::handle]: Executing action handlers for "campaign_interaction".
[21-Feb-2023 14:05:57 UTC] Array
(
    [title] => Registration Overlay
    [frequency] => always
    [placement] => center
    [has_registration_block] => 1
    [has_donation_block] => 
    [has_newsletter_block] =>
    [action] => form_submission
)

[21-Feb-2023 14:05:57 UTC] [NEWSPACK-DATA-EVENTS][Newspack\Data_Events::handle]: Executing action handlers for "campaign_interaction".
[21-Feb-2023 14:05:57 UTC] Array
(
    [title] => Registration Overlay
    [frequency] => always
    [placement] => center
    [has_registration_block] => 1 
    [has_donation_block] => 
    [has_newsletter_block] => 
    [action] => form_submission_success
)

10. Logout and visit the site again
11. Try to register again with the same email
12. Check your logs and see that you have the same events fired, but now the last one is form_submission_failure instead of success.
13. Repeat steps 5 to 9 but now with a Newsletters Subscription block.
14. On the logs, you should see has_newsletter_block as 1
15. Trying to subscribe to the same newsletter again with the same email won't trigger an failure - we don't consider this an error.

Other information:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes, as applicable?
• Have you successfully ran tests with your changes locally?

[dkoo]

Beautiful! The sequence of reporting via action hooks, form fields, and Data Events is very easy to follow.

[matticbot]

🎉 This PR is included in version 1.105.0-hotfix-hpb-amp-optimisations.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[matticbot]

🎉 This PR is included in version 1.106.0-alpha.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[matticbot]

🎉 This PR is included in version 1.106.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀