Domains: Remove CTAs from Gravatar flow

[rafaelgallani]

Proposed Changes

Prevents WordPress.com CTAs (set domain as primary, move domain to other site, map a domain, etc.) from being displayed in the Gravatar onboarding flow.

Why are these changes being made?

This is part of the Custom Domains on Gravatar project (pcYYhz-24z-p2).

Testing Instructions

• Access the Calypso live page or build this branch locally;
• Go to /start/domain-for-gravatar/domain-only?search=yes&new=your-test-domain.com;
• Search for a WordPress.com domain that is registered in another site;
• Try testing for both:
  • Search for a WordPress.com domain registration in a site you own;
  • Search for a standalone mapping in a WordPress.com site you own;
• Ensure you get error messages without any CTA (same as in the "Preview" section).

Preview

WordPress.com domain registered in another site

Standalone mapping in another 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)?

[github-actions]

Calypso Live (direct link)

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-108770&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

• blaze-dashboard
• command-palette-wp-admin
• odyssey-stats
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug add/prevent-domain-move-and-mapping-cta-for-gravatar-flow on your sandbox.

[matticbot]

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

Sections (~35 bytes added 📈 [gzipped])

name                  parsed_size           gzip_size
videopress-flow             +70 B  (+0.0%)      +35 B  (+0.0%)
update-design-flow          +70 B  (+0.0%)      +35 B  (+0.0%)
sensei-flow                 +70 B  (+0.0%)      +35 B  (+0.0%)
podcasts-flow               +70 B  (+0.0%)      +35 B  (+0.0%)
link-in-bio-tld-flow        +70 B  (+0.0%)      +35 B  (+0.0%)
domains                     +70 B  (+0.0%)      +35 B  (+0.0%)
copy-site-flow              +70 B  (+0.0%)      +35 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 (~35 bytes added 📈 [gzipped])

name                             parsed_size           gzip_size
async-load-signup-steps-domains        +70 B  (+0.0%)      +35 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.

[rafaelgallani]

We don't need to add new code to prevent Gravatar domains from being displayed as the "Domain Move" row in the search results, as these are already filtered by our back-end code.

[leonardost]

LGTM, tested and works as expected! 🚀