Site Migration: Add the possibility of exiting the Instructions step in the Assisted Migration flow

[valterlorran]

Related to #92260

Proposed Changes

• This PR adds two cards to offer the possibility of the user exiting the Instruction step after they go through the Assisted Migration flow.
• This PR should be shipped after: Site Migration: Add buttons to allow users to exit the Do-it-for-me flow dead-end #92290

Before

After

Why are these changes being made?

• We noticed that the instruction step after the Assisted Migration flow would leave the user on a Dead-end step without the possibility of redirecting them to further exploration of our platform.

Testing Instructions

• Apply this PR to your local environment or use the Calypso Live link below
• Navigate to /start and go through the migration flow until you reach the "What do you want to do?" step.
• Select "Migrate site"
• On the "How to migrate" step, select the "Do it for me" option
• Go through the checkout in case you are testing on a free site
• You should land on the assisted migration instruction step
• You should now see two cards on the bottom. Click on both of them and check that you are being redirected to the Customer Home page and the Support page.

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)?

[matticbot]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-112941

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-112941&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-112941&env=a8c-for-agencies

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

App Entrypoints (~2 bytes added 📈 [gzipped])

name           parsed_size           gzip_size
entry-stepper       +210 B  (+0.0%)       +2 B  (+0.0%)

Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used.

Sections (~716 bytes added 📈 [gzipped])

name                        parsed_size           gzip_size
import-hosted-site-flow        +11441 B  (+1.4%)    +3961 B  (+1.6%)
with-theme-assembler-flow        +360 B  (+0.6%)      +22 B  (+0.2%)
update-options-flow              +360 B  (+0.8%)      +21 B  (+0.4%)
update-design-flow               +360 B  (+0.0%)      +26 B  (+0.0%)
trial-wooexpress-flow            +360 B  (+0.8%)      +23 B  (+0.3%)
tailored-ecommerce-flow          +360 B  (+0.8%)      +20 B  (+0.3%)
site-setup-wg                    +360 B  (+0.5%)      +23 B  (+0.2%)
site-setup-flow                  +360 B  (+0.5%)      +23 B  (+0.2%)
site-migration-flow              +360 B  (+0.7%)      +21 B  (+0.2%)
readymade-template-flow          +360 B  (+0.2%)      +22 B  (+0.1%)
migration-signup                 +360 B  (+0.7%)      +18 B  (+0.2%)
import-flow                      +360 B  (+0.7%)      +21 B  (+0.2%)
hosted-site-migration-flow       +360 B  (+0.7%)      +22 B  (+0.2%)
free-post-setup-flow             +360 B  (+0.8%)      +20 B  (+0.4%)
free-flow                        +360 B  (+0.7%)      +21 B  (+0.2%)
entrepreneur-flow                +360 B  (+0.3%)      +21 B  (+0.1%)
assembler-first-flow             +360 B  (+0.5%)      +19 B  (+0.1%)
ai-assembler-flow                +360 B  (+0.5%)      +21 B  (+0.1%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• notifications

To test WordPress.com changes, run install-plugin.sh $pluginSlug add/exit-to-do-it-for-me-dead-end on your sandbox.

[a8ci18n]

This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/15937585

Some locales (Hebrew, Japanese) have been temporarily machine-translated due to translator availability. All other translations are usually ready within a few days. Untranslated and machine-translated strings will be sent for translation next Monday and are expected to be completed by the following Friday.

Thank you @valterlorran for including a screenshot in the description! This is really helpful for our translators.

[markbiek]

LGTM!