Move WPCOM_REST_API_Proxy_Request trait to the connection package

[manzoorwanijk]

Fixes #40947

Proposed changes:

• Move WPCOM_REST_API_Proxy_Request trait to the connection package
• Add an option to override $request_options to allow passing additional options like timeout

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

• Test the affected endpoints for self-hosted, AT and Simple sites. You can use the dev console.
• Hit these endpoints and verify that there are no PHP errors
• /wpcom/v2/email-preview

await wp.apiFetch({
    path: '/wpcom/v2/email-preview?post_id=32'
});

• /wpcom/v2/newsletter-categories

await wp.apiFetch({
    path: '/wpcom/v2/newsletter-categories'
});

• /wpcom/v2/newsletter-categories/count

await wp.apiFetch({
    path: '/wpcom/v2/newsletter-categories/count'
});

• /wpcom/v2/send-email-preview?id=32

await wp.apiFetch({
    path: '/wpcom/v2/send-email-preview?id=32',
    method: 'POST',
});

• Verify that you receive the email
• /wpcom/v3/blogging-prompts

await wp.apiFetch({
    path: '/wpcom/v3/blogging-prompts'
});

• /wpcom/v2/memberships/status

await wp.apiFetch({
    path: '/wpcom/v2/memberships/status',
});

• /wpcom/v2/memberships/products

await wp.apiFetch({
    path: '/wpcom/v2/memberships/products',
});

• Test those endpoints for a self-hosted site with an old version of the JP plugin and, e.g., Backups on this branch
• Do a sanity check for everything else

I also tested it on my Simple site

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the update/move-wpcom-rest-api-proxy-request-trait branch.

  • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack update/move-wpcom-rest-api-proxy-request-trait
  

  bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/move-wpcom-rest-api-proxy-request-trait
  

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen semi-continuously (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly. The next release is scheduled for February 4, 2025 (scheduled code freeze on undefined).

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[fgiannar]

Great work here, Manzoor!

Tested all endpoints with:

1. A self-hosted site on current branch
2. A simple site
3. A self-hosted site with latest Jetpack and Backups on this branch via Jetpack Beta

and everything works as expected 👍

Add an option to override $request_options( to allow passing additional options like timeout )

Since you added this, could you pls update the rest trait public methods accordingly?
Note that I didn't test this functionality since no endpoints are using the added argument yet.

[fgiannar]

LGTM 🚢