Untangling: polish UI components of the new IA

[fushar]

Fixes https://github.com/Automattic/dotcom-forge/issues/9865

Proposed Changes

This PR does the following:

• Promotes <Panel /> components to client/components so that they can be reused in other global view pages like Domains
• Adds max-width: 720px to the following pages:
  • Settings -> {all subtabs}
  • Advanced Tools -> {SFTP, Database}
• Resolves the upsell positioning issue (p1732287115632309-slack-CRWCHQGUB)
• Resolves the Site tools positioning issue in production (Untangling: apply new design to Settings -> Administration -> Reset your site #96488 (review))

Note

Sorry for the large number of changed files; it's mostly import changes 😭

Why are these changes being made?

pbxlJb-6ye-p2

Testing Instructions

1. Go to /sites.
2. Click a site.
3. Click around the subtabs and verify there are no visual issues.
4. Try with several site types.
5. Test also with ?flags=-untangling/hosting-menu flag turned offf.

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)?

[matticbot]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-125568

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[matticbot]

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

Sections (~252 bytes added 📈 [gzipped])

name                parsed_size           gzip_size
site-tools              +1058 B  (+0.1%)     +269 B  (+0.1%)
github-deployments       +881 B  (+0.1%)     +173 B  (+0.0%)
staging-site             +131 B  (+0.0%)      +30 B  (+0.0%)
hosting                  +130 B  (+0.0%)      +24 B  (+0.0%)
site-marketing            +93 B  (+0.0%)       -5 B  (-0.0%)
site-settings             -57 B  (-0.0%)       -9 B  (-0.0%)
settings                  -30 B  (-0.0%)      -41 B  (-0.0%)
marketing                 +17 B  (+0.0%)       -6 B  (-0.0%)
jetpack-social            +13 B  (+0.0%)       -2 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 (~23 bytes added 📈 [gzipped])

name                                       parsed_size           gzip_size
async-load-calypso-layout-command-palette        +70 B  (+0.0%)      +23 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 untangling/polish-ui on your sandbox.

[taipeicoder]

Tested around a LGTM 👍
I found an issue with the Marketing tab width on small screens, not sure if it's related to this but I didn't see the issue in wpcalypso.