fix(wcs): update subscriptions expiration cli behavior

[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:

This updates the wp newspack migrate-expired-subscription command behavior to schedule a final retry when the last retry took place within the sites on-hold duration.

How to test the changes in this Pull Request:

1. Make sure you DO NOT have the NEWSPACK_SUBSCRIPTIONS_EXPIRATION constant defined
2. If you don't already have any active subscriptions, as a reader purchase a handful of subscriptions
3. Follow the steps here to trigger scheduled retry for a handful of subscriptions: https://woocommerce.com/document/subscriptions/develop/failed-payment-retry/#section-7
4. Ensure you have at least two subscriptions that are on-hold and have gone through all possible retries
5. Define the NEWSPACK_SUBSCRIPTIONS_EXPIRATION constant: define( 'NEWSPACK_SUBSCRIPTIONS_EXPIRATION', true );
6. Now we want to set the last retry date for one of the subscriptions to sometime in the past that is greater than the sites on-hold duration (which defaults to 30 days). If you didn't have an old subscription to test on, you can manually do this via wp shell with the following:

$s=wcs_get_subscription(SUBSCRIPTION_ID);
$o=$s->get_last_order('all');
$retry=\WCS_Retry_Manager::store()->get_last_retry_for_order(wcs_get_objects_property($o, 'id'));
$retry->get_date_gmt(); // To get the date in gmt
$retry->update_date_gmt('2024-10-12 09:44:14'); // Replace date based on output from last step minus however many months to exceed on-hold duration

7. Via terminal, run the wp newspack migrate-expired-subscriptions --verbose --ids=1,2 command. ids should be the two subscriptions from above.
8. Confirm the output shows 1 subscription has been updated, and the other subscription has a retry scheduled.
9. Now run the command again with the --live flag.
10. Confirm the subscriptions have been updated accordingly, one set to expired and a new woocommerce_scheduled_subscription_payment_retry scheduled action added for the other.

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?

[leogermani]

Testing well!

[github-actions]

Hey @chickenn00dle, good job getting this PR merged! 🎉

Now, the needs-changelog label has been added to it.

Please check if this PR needs to be included in the "Upcoming Changes" and "Release Notes" doc. If it doesn't, simply remove the label.

If it does, please add an entry to our shared document, with screenshots and testing instructions if applicable, then remove the label.

Thank you! ❤️

[matticbot]

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

The release is available on GitHub release

Your semantic-release bot 📦🚀

[matticbot]

🎉 This PR is included in version 5.10.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀