Scheduled Updates: implement multi-site design on single site scheduled updates

[TimBroddin]

Related to #90401

Proposed Changes

Implements the design language of the multi-site design for single site scheduled updates.

Testing Instructions

Try this out on Calypso Live

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[matticbot]

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

App Entrypoints (~98 bytes removed 📉 [gzipped])

name                   parsed_size           gzip_size
entry-stepper               -305 B  (-0.0%)      -98 B  (-0.0%)
entry-main                  -305 B  (-0.0%)      -98 B  (-0.0%)
entry-subscriptions         -126 B  (-0.0%)      -30 B  (-0.0%)
entry-login                 -126 B  (-0.0%)      -30 B  (-0.0%)
entry-domains-landing       -126 B  (-0.0%)      -30 B  (-0.0%)
entry-browsehappy           -126 B  (-0.1%)      -30 B  (-0.1%)

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

Sections (~247 bytes removed 📉 [gzipped])

name                             parsed_size           gzip_size
plugins                             -13294 B  (-0.6%)    -3829 B  (-0.6%)
jetpack-cloud-plugin-management      -3926 B  (-0.3%)     -434 B  (-0.1%)

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.

[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 add/scheduled-updates-redesign on your sandbox.

[JanaMW27]

This looks good to me, minus one mino thing, in Calypso we don't use Recoleta for the headlines. On site specific we should use the non-recoleta typography.
Thannkkkkuuuuuuuuu

[ouikhuan]

• It feels like the heading in multi-site level is too large now. (compare with other A4A items like /sites) Also the text on multi-site level and site specific level is different. It shows "Update schedules" on mulitsite level and "Scheduled Updates" on site specific level.

• Should we align the text on New schedule and Add new schedule too?
• There's no margin for the save button on the site specific level page now, could we add some margin to it?
  

[TimBroddin]

• It feels like the heading in multi-site level is too large now. (compare with other A4A items like /sites) Also the text on multi-site level and site specific level is different. It shows "Update schedules" on mulitsite level and "Scheduled Updates" on site specific level.

My preference would be to change Update schedules to Scheduled Updates on multisite then. On single-site we already show "Scheduled Updates" in the menu, and it would be a bigger change to update the menus there. Also "Scheduled Updates" does ring a little bit better in my eyes. What do you think @ouikhuan?

• Should we align the text on New schedule and Add new schedule too?

I'll change it to New Schedule on single site too.

• There's no margin for the save button on the site specific level page now, could we add some margin to it?
  

👌

[ouikhuan]

Also "Scheduled Updates" does ring a little bit better in my eyes. What do you think @ouikhuan?

Sounds good, thanks!

[ouikhuan]

Looks good to me, thanks for addressing the feedback!