Forms: Add enableMailPoet attribute and toggle

[edanzer]

Fixes FORMS-205

Proposed changes:

Note: MailPoet integration is behind a feature flag. See test instructions.

This adds the block interface needed to enable MailPoet integration on a per-form basis. I'm following the way this works for Jetpack CRM and Salesforce. Specific changes:

• Adds a new connectMailPoet attribute to our forms
• Exposes a toggle on the MailPoet integration card that toggles connectMailPoet on/off
• When 'on' we display a MailPoet icon in the sidebar along with other active integrations
• Adds a separate MailPoet icon with orange background that looks better and works with the style of our active integration icons
• The value of connectMailPoet is added/saved as part of the block comment. In a separate PR, we'll add backend logic that uses this value, if true, to send contact details to MailPoet.

Screenshot

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

None.

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

No.

Testing instructions:

• Enable the feature flag with: add_filter( 'jetpack_forms_mailpoet_enable', '__return_true' );
• Add a form to page or post and open the integrations modal
• If needed, install and activate MailPoet from the integrations modal, and add a MailPoet key.
  • Before this is done, the toggle on the header to enable MailPoet should be disabled
  • After this is all done, the toggle on the header to enable MailPoet should be enabled
• Confirm that when you enable MailPoet via the toggle, the MailPoet icon is added to the list of active integrations in the sidebar.
• Question: my understanding is we do not need to worry about block deprecations when adding an attribute that is only saved to the block comment. If anyone knows differently, please let me know.

[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/forms-enableMailPoet-attribute branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/forms-enableMailPoet-attribute

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!

[jp-launch-control]

Code Coverage Summary

Coverage changed in 2 files.

File	Coverage	Δ%	Δ Uncovered
projects/packages/forms/src/blocks/contact-form/components/jetpack-integrations-modal/active-integrations/index.js	0/22 (0.00%)	0.00%	3 ❤️‍🩹
projects/packages/forms/src/blocks/contact-form/components/jetpack-integrations-modal/mailpoet-card.tsx	0/5 (0.00%)	0.00%	1 ❤️‍🩹

1 file is newly checked for coverage.

File	Coverage
projects/packages/forms/src/icons/mailpoet-orange.tsx	0/4 (0.00%) 💔

Full summary · PHP report · JS report

_{If appropriate, add one of these labels to override the failing coverage check: Covered by non-unit tests Use to ignore the Code coverage requirement check when E2Es or other non-unit tests cover the code Coverage tests to be added later Use to ignore the Code coverage requirement check when tests will be added in a follow-up PR I don't care about code coverage for this PR Use this label to ignore the check for insufficient code coveage.}