Site Migration: Show correct landing page when user ask for help

[gabrielcaires]

Closes #97664

Proposed Changes

• Move the user to the SITE_MIGRATION_SUPPORT_INSTRUCTIONS step when they ask if the platform is not supported and ask for help.
• Create a help ticket when the user clicks the support instructions step.

Why are these changes being made?

• As described in the original ticket, nowadays, when the user asks for help, we redirect the user to the regular SITE_MIGRATION_ASSISTED_MIGRATION, which says the migration will happen and also marks the migration as started.

Screenshots

Testing Instructions

• Go to any of the migration flows (e.g /setup/hosted-site-migration)
• Follow all steps by choosing the DIFM until the Tell us about your WordPress site
• Set any non-WordPress site
• On the Looks like there's been a mix-up step, click Looks like there's been a mix-up
• Check if you can see the migration-support-instructions step
• Check if a ticket was created (http call to /help/migration-ticket/new

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 UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• 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)?

[github-actions]

Calypso Live (direct link)

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[matticbot]

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

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

• notifications
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug fix/landing-page-when-user-ask-for-help on your sandbox.

[matticbot]

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

Sections (~18 bytes added 📈 [gzipped])

name                        parsed_size           gzip_size
import-hosted-site-flow          +304 B  (+0.0%)      +16 B  (+0.0%)
site-migration-flow               +42 B  (+0.1%)       +2 B  (+0.0%)
hosted-site-migration-flow        +42 B  (+0.1%)       +2 B  (+0.0%)

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.