#7732008 Copy Site: Prototype flow to copy an existing site

• Closes Automattic/dotcom-forge#1468

Proposed Changes

• Add a new Copy Site item on SMP site actions for atomic sites that you own.
• Create a new rough Copy Site flow to create a new site, buy a plan and migrate it to Atomic.

Testing Instructions

• If It’s not yet deployed, Apply and sandbox D97450-code.
• Go to /sites.
• On an atomic site you own, Click on the ellipsis action menu.
• Click on Create a copy of this site.
• Observe a new flow is open.
• Follow the steps, pay the plan, and observe a Success message after copying your site.

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• 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)?