Image CDN: Add compatibility with Breakdance editor

[dilirity]

Fixes HOG-333

Proposed changes:

• Fix images added via blocks from the Breakdance editor not being served through CDN.

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

HOG-333

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

no

Testing instructions:

• You need Breakdance from https://breakdance.com/ and Boost (free works) or Jetpack on a website that can run Image CDN. You'll have to sign up to breakdance to download the free version.
• After setting up Breakdance, make sure Image CDN is enabled either via the Boost settings or via Jetpack's Performance tab (Site accelerator), or via the Jetpack Modules page;
• Edit a page using the Breakdance editor and add an Image block (it might take a while for the blocks to load);

• Visit the page in the front-end and check the image URL - it should be served via CDN:

[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 WoA dev 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 (Jetpack), and enable the add/image-cdn/breakdance-compatibility branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/image-cdn/breakdance-compatibility

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 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 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

---

Jetpack plugin:

No scheduled milestone found for this plugin.

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

---

Boost plugin:

No scheduled milestone found for this plugin.

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

[jp-launch-control]

Code Coverage Summary

Coverage changed in 1 file.

File	Coverage	Δ%	Δ Uncovered
projects/packages/image-cdn/src/class-image-cdn-core.php	86/137 (62.77%)	-0.46%	1 ❤️‍🩹

1 file is newly checked for coverage.

File	Coverage
projects/packages/image-cdn/src/compatibility/breakdance.php	4/5 (80.00%) 💚

Full summary · PHP report · JS report

[LiamSarsfield]

LGTM! I can confirm this works as expected 🚀

Just 1 nit would be I wonder if we could add unit tests to this like Activitypub_Compat_Test.php

[dilirity]

@LiamSarsfield thanks. I've included a test for that.

I noticed the other compatibilities have a pattern to init their code on plugins_loaded instead of when the file is included. So I updated this compatibility to follow that.