Add educational content to the cancellation flow

[taggon]

Proposed Changes

As a part of the cancellation flow project( pebzTe-kL-p2 ), this PR adds educational content to the cancellation flow. The new content will be shown when a user picks specific answers. For more dedtails, check out pdZzpt-e9-p2.

Note that this PR is based on #69567. You should merge the preceding PR first.

Testing Instructions

• Attempt to cancel your paid plan.
• When you choose Technical issues > SEO issues, you should be able to see the educational content.
  
• The open question form will show up if you click on the Cancel my current plan button.

Other educational resources will like as follows:

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 #

[github-actions]

Calypso Live (direct link)

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

Jetpack Cloud live (direct link)

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

[JanaMW27]

Why the top nav is a bit different? there is no help access and the site name label is to the right rather than centered.

What I see:

What it should be:

And can we reduce the current space between the "Thanks, but this..." and the CTA?:

Thanks!

[dzver]

Overall works as expected. Left 3 questions about copy and styling.

[dzver]

I actually didn't test the test by a11n message because it's not part of the test plan. Should I have found a way to test it?

[taggon]

I actually didn't test the test by a11n message because it's not part of the test plan. Should I have found a way to test it?

@dzver See pebzTe-sj-p2 😄

[matticbot]

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

Sections (~2081 bytes added 📈 [gzipped])

Details

name            parsed_size           gzip_size
site-purchases      +8574 B  (+0.6%)    +2081 B  (+0.6%)
purchases           +8574 B  (+0.5%)    +2081 B  (+0.4%)
domains             +8574 B  (+0.5%)    +2081 B  (+0.5%)

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.

[a8ci18n]

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

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

[dzver]

I checked all the copy and the code and it looks good to me but I still see a merge conflict.

[dzver]

This might not quite apply if they're on a monthly plan and cancelling it but I think we can ship and iterate if this step turns out to be successful.

[taggon]

cc @JanaMW27

[taggon]

Rebased.

[taggon]

Rebased

[a8ci18n]

Translation for this Pull Request has now been finished.