Domains Management Revamp: Add email plans comparison subpage to site context

[phcp]

Closes #98275

Proposed Changes

• Add email plans comparison subpage to the site context.

Why are these changes being made?

• This is part of the Domain Management Revamp project: pfuQfP-13x-p2

Testing Instructions

• Apply this PR to your local
• Go to http://calypso.localhost:3000/sites?flags=calypso/all-domain-management.
• Click on a site with a domain previously configured and without email configured.
• Scroll down to the domains table and click on the domain.
• You should see the domain overview page within the site context.
• Click on the Email tab.
• Click on "See how they compare" link.
• The plans comparison page should be rendered in the site context.
• Select one of the email plans.
• It should return to the Email overview page with the correct plan expanded, and it should continue in the site context.
• Go back to the plans comparison page.
• Switch to Monthly plans and select a different plan.
• It should return to the Email overview page with the correct interval selected and the plan expanded, and it should continue in the site context.
• Test the navigation using the breadcrumb, it should continue in the site context.
• Perform regression tests in the domain context.
• The page should behave the same, and the navigation should stay within the domain context.
• Go to the old UI and perform regression tests (WP Admin -> Hosting -> Email).
• The page should work as before, without changes in visual or behavior.

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-129910

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-129910&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 (~50 bytes removed 📉 [gzipped])

name                   parsed_size           gzip_size
entry-main                   -49 B  (-0.0%)      -26 B  (-0.0%)
entry-login                  -49 B  (-0.0%)      -26 B  (-0.0%)
entry-domains-landing        -49 B  (-0.0%)      -25 B  (-0.0%)

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

Sections (~19 bytes removed 📉 [gzipped])

name                  parsed_size           gzip_size
hosting                    +191 B  (+0.0%)       +3 B  (+0.0%)
update-design-flow          -49 B  (-0.0%)      -22 B  (-0.0%)
link-in-bio-tld-flow        -49 B  (-0.0%)      -22 B  (-0.0%)
copy-site-flow              -49 B  (-0.0%)      -22 B  (-0.0%)
email                       +14 B  (+0.0%)       +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.

Async-loaded Components (~72 bytes removed 📉 [gzipped])

name                                                                              parsed_size           gzip_size
async-load-signup-steps-page-picker                                                     -49 B  (-0.0%)      -25 B  (-0.0%)
async-load-signup-steps-domains                                                         -49 B  (-0.0%)      -22 B  (-0.0%)
async-load-purchase-modal-wrapper                                                       -49 B  (-0.0%)      -25 B  (-0.0%)
async-load-my-sites-checkout-purchase-modal-is-eligible-for-one-click-checkou...        -49 B  (-0.0%)      -25 B  (-0.0%)
async-load-calypso-my-sites-checkout-modal                                              -49 B  (-0.0%)      -25 B  (-0.0%)

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

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.

[bogiii]

I have tested the flow inside the site context and works as described.
Anyway, I found one issue in the domains context with the breadcrumbs email link. It redirect to the old UI.

We probably need to build a URL relative to the current route. You can see how I recently handled for some other cases.

https://github.com/Automattic/wp-calypso/blob/trunk/client/my-sites/domains/domain-management/subpage-wrapper/headers/add-mailbox-header.tsx#L29-L31

[Imran92]

Looks good!

The only issue I saw is in domain context, the Email breadcrumb takes the user fully out of the revamped context

[phcp]

@Imran92 @bogiii, nice catch! I just pushed a fix for that, also fixed on the Email Forwarding page.

[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/domains-management-compare-email-providers on your sandbox.