Site Migration: Redirect to new site migration flow from MTWPCOM

[andres-blanco]

paYKcK-4Uz-p2

Proposed Changes

When clicking on the Get started button in the Move to WPCOM plugin on a disconnected site, you are redirected to /setup/import-focused/migrationHandler which triggers the old Jetpack migration process. While the redirect [mc-link]/jetpack-crew/redirects/ is correctly loaded on this tool, it does not seem to be working when navigating through the authorization flow.

This diff changes that behaviour to point to the /setup/hosted-site-migration.

Why are these changes being made?

We are attempting to bring down to zero migrations via the Jetpack flow. This will help with that.

Testing Instructions

• Create JN site
• Install & activate the Move to WordPress.com plugin
• Go to the plugin page in wp-admin
• Click the Get started CTA
• Once you get to the authorization page change wordpress.com in the URL by the calypso.live link below or calypso.localhost:3000 if testing locally
• Press enter to reload the page
• Authorize the plugin
• Verify you are arrive at /setup/hosted-site-migration/site-migration-identify?ref=jetpack-connect&from=[JN_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-aUh-p2)?