Feature: add Constant Contact add-on to the form migration process

[JoshuaHungDinh]

Resolves: GIVE-176

Description

This PR includes a form migration step for the new Constant Contact block migrating from a v2 form to a v3 form. I also removed the commented section of supported addons for Constant Contact so that it will display on our list when upgrading.

Cases when the block should be added.

• While Constant Contact is globally enabled on all forms, if the form is not explicitly disabled from the per form setting migrating should add the block.
• While Constant Contact is not globally enabled if it is explicitly enabled on the per form setting than migrating should add the block.

Testing Instructions with updated visuals

ConsatantContact-FOIRM-SETTINGS.mov

GlLOBAL-SETTINGS.mov

• Use New Constant Contact Block
  
• Set your global settings
• add a v2 form -> then migrate the form without editing the form settings.
• Verify the v3 form has the correct settings set from the global options.
• Create another v2 form -> update the per-form settings on the right -> then migrate the form
• Verify the v3 form has the correct settings set from the form options.

Pre-review ChecklistT

• Relevant @unreleased tags included in DocBlocks
• Reviewed by the designer (if follows a design)
• Self Review of code and UX completed

[alaca]

Looks good 👍

[jonwaldstein]

@JoshuaHungDinh great job man!! You are a unit test writing machine now 🤩

[rickalday]

Passed QA tests.