Add settings page redirects to wp-admin for duplicate view experiment

[okmttdhr]

Related to #98875, Automattic/jetpack#40913, #98664

Proposed Changes

This is a follow-up for #98875, redirecting settings pages from Calypso to wp-admin when the experiment is enabled.

Note

It'd be nicer to deploy this PR after Automattic/jetpack#40913 lands on Atomic.

Why are these changes being made?

Please refer to p7DVsv-mbN-p2

Testing Instructions

• Add yourself to the treatment group via 22167-explat-experiment
• Prepare a site with the Default interface style
• Observe the following redirections:

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[matticbot]

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

Sections (~187 bytes added 📈 [gzipped])

name                  parsed_size           gzip_size
settings-discussion        +101 B  (+0.0%)      +31 B  (+0.0%)
settings-writing            +98 B  (+0.0%)      +37 B  (+0.0%)
settings-reading            +98 B  (+0.0%)      +38 B  (+0.0%)
settings-security           +66 B  (+0.0%)      +16 B  (+0.0%)
settings-podcast            +66 B  (+0.0%)      +30 B  (+0.0%)
settings-performance        +66 B  (+0.0%)      +19 B  (+0.0%)
settings-newsletter         +66 B  (+0.0%)      +30 B  (+0.0%)
settings-jetpack            +66 B  (+0.0%)      +22 B  (+0.0%)
settings                    +66 B  (+0.0%)      +24 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.

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/wp-admin-redirects on your sandbox.

[lsl]

I think this redirect is wrong, we should be updating the classic view menu item on the JP side instead of doing a redirect here. Will follow up.

I'd like it if /settings/general always redirects to options-general.php no matter what site / view you're on.

At the moment, /settings/general will take you to two different places depending on if you're classic view or not.

[lsl]

#99391

[lsl]

Tested each of these redirects, lets follow up to remove the special case redirect on classic view /settings/general