Paid stats: add Stats reference on Personal checkout

[Initsogar]

Resolves https://github.com/Automattic/red-team/issues/305

We want to include Stats features on the checkout page while purchasing a WordPress.com Personal plan.

To achieve this, we need to replace the existing feature texts from FEATURE_STATS_PAID with FEATURE_STATS_COMMERCIAL and add the new feature message for FEATURE_STATS_PAID on the checkout page.

To ensure a smooth transition, these changes are being made conditionally under the stats/paid-wpcom-v3 feature flag to ensure everything works as expected.

Note

Due to restrictions on how the features list is presented, I am merging both lines into a single line while we gather feedback from the design team. I believe it is safe to proceed with this PR and iterate if needed.

Expected	Proposal

Proposed Changes

• Add FEATURE_STATS_COMMERCIAL feature details using the existing FEATURE_STATS_PAID.
• Update FEATURE_STATS_PAID title/description with the new texts under the stats/paid-wpcom-v3 feature flag.
• Replace FEATURE_STATS_PAID with conditional logic to use FEATURE_STATS_COMMERCIAL under the stats/paid-wpcom-v3 feature flag in the Calypso plans list configuration.
  • This ensures that any references to FEATURE_STATS_PAID will continue working as usual and will switch to FEATURE_STATS_COMMERCIAL when the feature flag is enabled.

Before	After

Why are these changes being made?

https://github.com/Automattic/red-team/issues/305

Testing Instructions

• Spin up a Calypso Live Branch

Validate Personal checkout has the new message under stats/paid-wpcom-v3 flag

• Try upgrading to Personal plan. You can click on Upgrade plan on Clicks module.
• Ensure you see the Stats beyond last 7 days message in the features list (the feature flag is enabled by default in live branch environment).
  
• Now disable the feature flag by appending ?flags=-stats/paid-wpcom-v3 to the checkout page.
• Ensure you don't see any Stats message in the features list.
  

Validate Premium checkout is not affected

• Try upgrading to Premium plan, you can click on Upgrade plan on the UTM or Devices module.
• In the checkout page, ensure you see In-depth site analytics dashboard. in the features list, with and without the stats/paid-wpcom-v3 flag.
  

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

• happy-blocks
• help-center
• notifications
• odyssey-stats
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug update/stats-personal-checkout on your sandbox.

[matticbot]

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

App Entrypoints (~93 bytes added 📈 [gzipped])

name           parsed_size           gzip_size
entry-stepper       +660 B  (+0.0%)      +93 B  (+0.0%)
entry-main          +660 B  (+0.0%)      +93 B  (+0.0%)
entry-login         +660 B  (+0.0%)      +93 B  (+0.0%)

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

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.

[kangzj]

Works as described 👍

[a8ci18n]

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

Some locales (Hebrew, Japanese) have been temporarily machine-translated due to translator availability. All other translations are usually ready within a few days. Untranslated and machine-translated strings will be sent for translation next Monday and are expected to be completed by the following Friday.

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

[a8ci18n]

Translation for this Pull Request has now been finished.