Screen options: Handle switches to WP Admin views

[mmtr]

Fixes #53708

Changes proposed in this Pull Request

Handles clicks on the new screen switcher component and redirect users to WP Admin when the Classic view is selected.

Testing instructions

• Use the Calypso live link below and append ?flags=nav-unification/switcher to the end of the URL.
• Switch to a Simple or Atomic site.
• In the following screens, make sure that opening the Screen Options tab and clicking on "Classic view" redirects you to the equivalent WP Admin screen.
  • My Home
  • Posts > All posts
  • Posts > Categories
  • Posts > Tags
  • Media
  • Pages > All pages
  • Testimonials > All testimonials
  • Portfolio > All projects
  • Comments
  • Appearance > Themes
  • Users > All users
  • Tools > Import
  • Tools > Export
  • Settings > General
  • Settings > General > Writing
  • Settings > General > Discussion
• Make sure the WP Admin links include a preferred-view=classic param (which will be used in a future diff for storing the new preference).
• Switch to a Jetpack site.
• Make sure the quick switcher doesn't show up.

[matticbot]

Link to Calypso live: https://calypso.live?image=registry.a8c.com/calypso/app:build-8584
Link to Jetpack Cloud live: https://calypso.live?image=registry.a8c.com/calypso/app:build-8584&env=jetpack

[matticbot]

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

Sections (~2612 bytes added 📈 [gzipped])

name                 parsed_size           gzip_size
settings-writing          +697 B  (+0.1%)     +199 B  (+0.1%)
posts-custom              +667 B  (+0.1%)     +225 B  (+0.2%)
pages                     +662 B  (+0.2%)     +222 B  (+0.2%)
settings-discussion       +661 B  (+0.3%)     +202 B  (+0.3%)
settings                  +658 B  (+0.1%)     +198 B  (+0.1%)
comments                  +656 B  (+0.1%)     +210 B  (+0.1%)
themes                    +649 B  (+0.2%)     +194 B  (+0.2%)
media                     +649 B  (+0.1%)     +173 B  (+0.1%)
export                    +649 B  (+0.4%)     +209 B  (+0.4%)
home                      +648 B  (+0.2%)     +200 B  (+0.2%)
posts                     +647 B  (+0.1%)     +185 B  (+0.1%)
import                    +622 B  (+0.3%)     +213 B  (+0.3%)
people                    +621 B  (+0.2%)     +182 B  (+0.2%)

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.

[tjcafferkey]

Just left a few minor comments but overall LGTM and works as expected. Thanks for adding the additional component tests too 🙌🏻

[a8ci18n]

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

Hi @mmtr, could you please edit the description of this PR and add a screenshot for our translators? Ideally it'd include all of the following strings:

• Our WordPress.com redesign for a better experience.
• The classic WP-Admin WordPress interface.

Thank you in advance!

[a8ci18n]

Translation for this Pull Request has now been finished.