Multi-year Plans Default Experiment: Ensure only the onboarding flow is eligible

[jeyip]

Proposed Changes

• Introduces changes to the useLongerPlanTermDefaultExperiment hook and adds an optional flowName parameter.
• This parameter is used to ensure only the onboarding flow displays the multi-year plans by default experiment changes.

Why are these changes being made?

• We only want to target /setup/onboarding/plans and /start/plans

Testing Instructions

• Manually assign self to an experiment variant default_to_three_year_plans, default_to_two_year_plans, emphasize_savings_only 22092-explat-experiment
• Visit /setup/onboarding/plans and verify that the savings emphasis badges and multi-year plan term defaults behave as expected
• Visit a different flow, like /setup/newsletter/plans or /start/onboarding-pm/plans and verify that the savings emphasis badges and multi-year defaults aren't displayed

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-130236&env=a8c-for-agencies

[matticbot]

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

Sections (~14 bytes removed 📉 [gzipped])

name                  parsed_size           gzip_size
update-design-flow          +46 B  (+0.0%)      -14 B  (-0.0%)
plugins                     +46 B  (+0.0%)      -14 B  (-0.0%)
plans                       +46 B  (+0.0%)      -14 B  (-0.0%)
link-in-bio-tld-flow        +46 B  (+0.0%)      -14 B  (-0.0%)
jetpack-app                 +46 B  (+0.0%)      -14 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 (~9 bytes removed 📉 [gzipped])

name                                             parsed_size           gzip_size
async-load-signup-steps-plans-theme-preselected        +47 B  (+0.0%)      -12 B  (-0.0%)
async-load-signup-steps-plans                          +47 B  (+0.0%)      -11 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.

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• notifications
• wpcom-block-editor

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