Update woo passwordless screens

[chihsuan]

We reverted #87931 in #88260, which not only reverted the "Continue as Existing user" screen but also reverted the CSS changes of other passwordless screens.

This PR is to bring back the "Continue as Existing user" screen in passwordless feature flag and also fix the other passwordless screens.

Proposed Changes

• Bring back the new "Continue as Existing user" screen in passwordless feature flag.
• Fix the styles of other passwordless screens to match the design.
• Update Term of Service.
• Change all wooPasswordless props name to isWooPasswordless.

Testing Instructions

Please setup woo start env for testing

Passwordless signup

1. Use incognito mode
2. Go to the Woo Express site creation flow (https://woo.com/start/#/installation > Try Woo Express for free)
3. Observe that signup screen matches the design 4ixWMlzrxllx93tSFsCW6k-fi-9483_4315

Continue as Existing user

1. Log in to WP.com but Log out of Woo.com
2. Go to the Woo Express site creation flow
3. Observe that the "Continue as Existing user" screen matches the design (4ixWMlzrxllx93tSFsCW6k-fi-9483%3A13771)

"Check your email" screen

• Go to https://wordpress.com/log-in/link?redirect_to=https%3A%2F%2Fpublic-api.wordpress.com%2Foauth2%2Fauthorize%2F%3Fresponse_type%3Dcode%26client_id%3D50916%26state%3Dcc209140df814f02119fcc56e3662fbb82d946f1631feeca2c5290f408c83029%26redirect_uri%3Dhttps%253A%252F%252Fwoo.com%252Fwc-api%252Fwpcom-signin%253Fnext%253D%25252F%26blog_id%3D0%26wpcom_connect%3D1%26wccom-from%3Dnux%26calypso_env%3Dproduction%26from-calypso%3D1&client_id=50916&woo-passwordless=yes
• Enter an email or username (non-a8c account) and click "Send link"
• Observe that the "Check your email" screen matches the design 4ixWMlzrxllx93tSFsCW6k-fi-9483%3A8624

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• https://wpcalypso.wordpress.com/devdocs/docs/testing/index.md 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-100733

Jetpack Cloud live (direct link)

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

[matticbot]

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

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

name         parsed_size           gzip_size
entry-login      +1508 B  (+0.1%)     +220 B  (+0.1%)

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

Sections (~231 bytes added 📈 [gzipped])

name             parsed_size           gzip_size
jetpack-connect      +1549 B  (+0.1%)     +231 B  (+0.1%)
accept-invite        +1186 B  (+0.6%)     +156 B  (+0.3%)

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 (~394 bytes added 📈 [gzipped])

name                          parsed_size           gzip_size
async-load-design-blocks          +1508 B  (+0.1%)     +243 B  (+0.0%)
async-load-signup-steps-user      +1191 B  (+0.8%)     +151 B  (+0.4%)

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

• wpcom-block-editor

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

[ilyasfoo]

Tests well, but I have a minor question. 🚢

[ilyasfoo]

I wonder why this change is needed? I'm not seeing any consumers passing a node 🤔

[chihsuan]

Because we changed the submitButtonLoadingLabel, I think it would be a bit odd/confusing for these two to have different prop types. So, I changed this to ensure consistency. Does that sound good?

[ilyasfoo]

I see. That makes sense, LGTM!

[moon0326]

LGTM and tested well 👍 🚀

[a8ci18n]

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

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 @chihsuan for including a screenshot in the description! This is really helpful for our translators.

[a8ci18n]

Translation for this Pull Request has now been finished.