Podcast: scaffold empty package + module behind feature flag (1/4)

[arcangelini]

PR 1 of 4 in the Podcast untangle train.

Proposed changes

Adds an empty projects/packages/podcast package, registers it as a Jetpack composer dependency, and calls Podcast::init() from Jetpack::late_initialization() in class.jetpack.php (alongside Scan_Page_Init::initialize()). The module is gated on Simple/Atomic hosts and behind the new jetpack_podcast_untangle filter (default false), so it has no runtime effect until subsequent PRs in the train fill it in.

Upstream consolidation PR: #48499

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

No.

Testing instructions

This is just wiring things up there is nothing observable. Just basic smoke check.

[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 or WordPress.com Site Helper), and enable the add/podcast-package-scaffold branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/podcast-package-scaffold

bin/jetpack-downloader test jetpack-mu-wpcom-plugin add/podcast-package-scaffold

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

[jp-launch-control]

Code Coverage Summary

Coverage changed in 1 file.

File	Coverage	Δ%	Δ Uncovered
projects/plugins/jetpack/class.jetpack.php	748/2277 (32.85%)	-0.01%	1 ❤️‍🩹

Full summary · PHP report · JS report