Protect: Rename plugin Composer package and add packages/protect

[jboland88]

Proposed changes

• Rename the Protect plugin's Composer package to automattic/jetpack-protect-plugin, as was done for Search, Backup and VideoPress.
• Add an empty packages/protect package (automattic/jetpack-protect, namespace Automattic\Jetpack\Protect_Package) for shared Protect code, such as the dashboard in Protect Dashboard: Add a feature-flagged module that takes over the Protect page #53182.

Related product discussion/links

• Follows the Search precedent in Search: Create a new search package, rename Search plugin #21502.
• Needs the Automattic/jetpack-protect mirror repo before merging. That name currently redirects to jetpack-protect-plugin.

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

No.

Testing instructions

• Confirm CI passes. Nothing should change at runtime.
• jp build plugins/protect should still build, and the plugin should still load on a test site.

🤖 Generated with Claude Code

[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 update/protect-package-name branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack update/protect-package-name

bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/protect-package-name

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!

---

Protect 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

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report