Incompatible Plugins update: Remove wpcom-migration, add duplicator-pro

[villanovachile]

Fixes: #1141 & #1105

Proposed changes:

Updates the incompatible plugins array to:

• add duplicator-pro, which causes fatals on dotcom
• remove wpcom-migration which is no longer incompatible and will be required for incoming migrations

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

No

Testing instructions:

• Follow the steps to test this branch (should be a comment posted by the bot below)
• On your WoA dev site, Install wpcom-migration by running the wp-cli command wp plugin install wpcom-migration
• Navigate to /wp-admin/plugins.php and confirm that the plugin is able to be activated (should not be disabled)
• Create a dummy plugin in ~/htdocs/wp-content/plugins/duplicator-pro/duplicator-pro.php with the following:

<?php
/**
 * Plugin Name: Duplicator Pro
 * Plugin URI:  http://na.com                     
 * Description: Duplicator Pro dummy plugin
 * Version:     1.0
 * Author:      villanovachile
 * Author URI:  http://na.com     
 */

• Navigate to /wp-admin/plugins.php and confirm that the plugin is disabled and cannot be activated

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

---

Wpcomsh plugin:

• Next scheduled release: Atomic deploys happen twice daily on weekdays (p9o2xV-2EN-p2).

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

[markbiek]

LGTM!

[villanovachile]

LGTM!

Now these will need to be added to Calypso. I'lll tag ya there once I got that done. Thanks again!