Domains: Remove email restrictions for Gravatar domains

[leonardost]

Related to https://github.com/Automattic/nomado-issues/issues/1243

Proposed Changes

This PR removes email restrictions from Gravatar domains. This means that now free Gravatar domains can have Professional email attached to them if the user pays for it.

This PR basically reverts the Professional email restrictions added in #96085.

This is part of the Gravatar Domains i3 project (pcYYhz-2vx-p2).

Why are these changes being made?

We want to allow free Gravatar domain owners to attach email to their domains, but only if they pay for it in order to prevent abuse.

Testing Instructions

This depends on 172418-ghe-Automattic/wpcom.

Go to the domain management page for a domain that has both the usage_gravatar and usage_gravatar_restricted domain flags

• Ensure the Professional email purchase CTA is shown on the right column:

• Ensure the free 3-month introductory offer is not available:

• Ensure the checkout price also looks correct:

Now try to purchase Professional email for a domain that has only the usage_gravatar flag, i.e. it's a free Gravatar domain that was renewed.

• Ensure the 3-month introductory offer is available:

• Ensure the introductory offer is also correct in checkout:

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-132200&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
• help-center
• notifications
• odyssey-stats
• whats-new
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug update/email-restrictions-for-gravatar-domains on your sandbox.

[matticbot]

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

Sections (~200 bytes removed 📉 [gzipped])

name      parsed_size           gzip_size
hosting        -817 B  (-0.0%)     -200 B  (-0.0%)
domains        -817 B  (-0.0%)     -200 B  (-0.0%)
email          -796 B  (-0.1%)     -201 B  (-0.1%)
checkout       -524 B  (-0.0%)     -126 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.