Couple bug fixes for ESP sync CLI command

[claudiulodro]

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:

Note: This is a hotfix PR.

This PR fixes a couple bugs in the ESP sync CLI command.

1. The parser did not like the ellipses in the docs like [--subscription-ids=<id1,id2...>], so those parameters weren't getting recognized.
2. When an error was thrown during sync, the command threw a fatal error because the $customer object didn't exist.

How to test the changes in this Pull Request:

1. Before applying this PR try e.g. wp newspack esp sync --user-ids=1. Observe the following output:

Warning: The `wp newspack esp sync` command has an invalid synopsis part: [--subscription-ids=<id1,id2...>]
Warning: The `wp newspack esp sync` command has an invalid synopsis part: [--user-ids=<id1,id2...>]
Warning: The `wp newspack esp sync` command has an invalid synopsis part: [--order-ids=<id1,id2...>]
Error: Parameter errors:
 unknown --user-ids parameter

2. Add the following to the top of ESP_Sync::sync_contact so an error is always thrown:

	return new \WP_Error(
		'newspack_esp_sync_contact',
		sprintf(
		// Translators: %d is the user ID.
			__( 'Customer with ID %d does not exist.', 'newspack-plugin' ),
			1
		)
	);

3. Run wp newspack esp sync. Observe output like the following:

[11-Dec-2024 00:10:05 UTC] PHP Fatal error:  Uncaught Error: Call to a member function get_email() on null in /Users/claudiulodro/Local Sites/newspackdev/app/public/wp-content/plugins/newspack-plugin/includes/cli/class-ras-esp-sync.php:229
...

3. Apply this patch. Verify that the --user-ids flag works and that when an error is thrown you now get something like Error syncing contact info for user ID 3. Customer with ID 1 does not exist instead of a fatal 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?

[matticbot]

🎉 This PR is included in version 5.9.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀