feat(metering): dispatch RAS activity on content restriction

[miguelpeixe]

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:

1200550061930446-as-1208347477266676/f

Because our content restriction strategy implements new layers on top of Woo Memberships for metered content restriction, we don't fully support 3rd parties to leverage our implementation for their content features.

2 public methods can already be used to detect content restriction on the Newspack side:

• Newspack\Memberships::is_post_restricted( $post_id );: whether the post is restricted on the backend.
• Newspack\Memberships\Metering::is_metering();: whether the restricted post (method above) should be allowed to render due to metering rules. This will always be reading from the global $post and should only be used in a is_singular() context.

The second method will also return true if the metering is supposed to happen in the front-end (anonymous metering). That's what we don't have an API for.

This PR proposes this API to be a listener on a RAS activity dispatch so that it can be used like this:

window.newspackRAS = window.newspackRAS || [];
window.newspackRAS.push( ras => {
	ras.on( 'activity', function( ev ) {
		const { action, data } = ev.details;
		if ( 'metering_restricted' === action ) {
			// Do stuff here.
			console.log( data );
		}
	} );
} );

The data payload:

{
  "post_id": "117",          // Restricted post ID
  "metering": {              // Current metering configuration for the reader
    "content": [             // List of allowed post IDs
      "122"
    ],
    "expiration": 1726887600 // Metering expiration
  }
}

How to test the changes in this Pull Request:

1. Make sure you have RAS configured with Woo Memberships and content gating
2. Edit your content gate to allow metered access of 1 post for anonymous readers
3. In a fresh session, visit 2 articles so you hit the gate
4. Open DevTools, inspect localStorage, and confirm the np_reader_1_activity item includes a metering_restricted activity with the data payload as exemplified above

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]

Nice and simple solution using the reader data API!

[matticbot]

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

The release is available on GitHub release

Your semantic-release bot 📦🚀

[matticbot]

🎉 This PR is included in version 5.6.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀