fix(parse.ly): update meta_type default

[chickenn00dle]

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:

Closes https://linear.app/a8c/issue/NPPM-2833/possible-conflict-between-yoast-and-our-required-parsely-code-that-may

This PR updates the default meta_type parse.ly config to repeated_metas which is recommended by parse.ly . This also implements a migrator so existing sites with Parse.ly get the updated setting.

We need to do this to avoid the conflict pointed out in the linear task above when Yoast is active.

Removing parsely
These tests will require removing parsely and parsely settings several times. You can do so with the following:

wp plugin delete wp-parsely
wp option delete parsely

1. On release, add the following snippet to a site where parsely is removed:

add_action( 'init', function(){
	$request = new WP_REST_Request( 'POST', '/newspack/v1/plugins/wp-parsely/configure' );
	$response = rest_do_request( $request );
} );

2. Reload the page and go to Parsely settings.
3. Confirm you see json_ld selected for Metadata Format:

4. Checkout this branch and reload the page
5. Confirm Metadata Format is now set to repeated_metas
6. Now remove parsely once again
7. Ensure the snippet from step 1 is still present, then reload the page. (You'll likely need to navigate away and back again to the parsely settings page if you removed following the steps above)
8. Confirm Metadata Format is set to repeated_metas

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?

[Copilot]

Pull request overview

This PR updates Newspack’s automated configuration defaults for the Parse.ly plugin to use Parse.ly’s recommended meta_type setting (repeated_metas), intended to avoid the Yoast conflict referenced in NPPM-2833.

Changes:

• Change the default Parse.ly setting meta_type from json_ld to repeated_metas when Newspack initializes Parse.ly settings for the first time.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[chickenn00dle]

Just noting the lint failure was fixed here in trunk: #4718