#7644992 Split pricing plans block by plan

Proposed Changes

This pull request splits the Pricing Plans block into three separate blocks (backed by the same implementation) that allow for faster usage by having each one provide different default plan. Plans can still be customised from the block settings if desired.

Testing Instructions

• Run yarn dev --sync in apps/happy-blocks to sync code to your sandbox
• Create a new topic, in the editor press / and search for “Upgrade” block.
• On your sandbox, edit wp-content/themes/a8c/supportforums/editor/gutenberg-wpcom.php and add to the function supportforums_gutenberg_setup_frontend before return $settings; line:

$settings['iso']['blocks']['allowBlocks'][] = 'happy-blocks/pricing-plans-premium';
$settings['iso']['blocks']['allowBlocks'][] = 'happy-blocks/pricing-plans-business';
$settings['iso']['blocks']['allowBlocks'][] = 'happy-blocks/pricing-plans-ecommerce';

• Ensure the three different plan options show up, and each one creates a block with the correct pricing plan pre-selected
• Publish the post and ensure the view of the block shows correctly.

Pre-merge Checklist

• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the “[Status] String Freeze” label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• For changes affecting Jetpack: Have we added the “[Status] Needs Privacy Updates” label if this pull request changes what data or activity we track or use (p4TIVU-ajp-p2)?

Related to #