Boost: Exclude builder plugins' post types from Critical CSS

[dilirity]

Fixes HOG-184

This is a collection of post types that we've received complaints for. Some are registered correctly, but I added them anyway, to avoid having to patch Boost if down the line a plugin messes up their post type registration.

Divi Builder isn't in the list, as the custom post types it registers aren't available when Source Providers are collected.

I didn't outline testing instructions as most plugins are premium and the steps to make posts from their post types show in the source providers list are quite lengthy.

Proposed changes:

• Exclude post types of popular builder plugins from Critical CSS generation:
  • Beaver Builder;
  • Breakdance;
  • Elementor (already present, just added another post type).

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

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

no

Testing instructions:

N/A

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

---

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 2 files.

File	Coverage	Δ%	Δ Uncovered
projects/plugins/boost/jetpack-boost.php	0/114 (0.00%)	0.00%	4 💔
projects/plugins/boost/compatibility/elementor.php	0/11 (0.00%)	0.00%	2 ❤️‍🩹

2 files are newly checked for coverage.

File	Coverage
projects/plugins/boost/compatibility/beaver-builder.php	0/5 (0.00%) 💔
projects/plugins/boost/compatibility/breakdance.php	0/6 (0.00%) 💔

Full summary · PHP report · JS report

_{Coverage check overridden by I don't care about code coverage for this PR Use this label to ignore the check for insufficient code coveage. .}