Enable logged out for /me/account/closed

[candy02058912]

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

Proposed Changes

• Enable logged out for /me/account/closed
• Added redirection back to /me when accessing an unexisting /me route, for example /me/abcde redirects back to login page if logged out and redirects to /me when logged in

Note that this page currently defaults to the "Account is deleting" state but it's actually not doing anything. We can address it after merging https://github.com/Automattic/wp-calypso/pull/96446

Why are these changes being made?

• Allow users to self-restore accounts pet6gk-1Em-p2

Testing Instructions

• Checkout this diff and rerun yarn start (this is a must for the changes to be reflected)
• You are logged out
• Go to calypso.localhost:3000/me/account/closed and it should be accessible
• The other /me routes and will redirect to `/log-in?redirect_to=

I've checked the important /me routes I could find in wp-calypso

• [ ] /me
• [ ] /me/account
• [ ] /me/account/close
• [ ] /me/account/closed
• [ ] /me/profile
• [ ] /me/public-profile
• [ ] /me/trophies
• [ ] /me/find-friends
• [ ] /me/get-apps
• [ ] /me/quickstart
• [ ] /me/concierge
• [ ] /me/developer
• [ ] /me/chat
• [ ] /me/notifications
• [ ] /me/privacy
• [ ] /me/purchases
• [ ] /me/purchases/add-credit-card
• [ ] /me/billing
• [ ] /me/purchases/billing
• [ ] /me/purchases-by-owner (this currently is a blank page on production if it's not /me/purchases-by-owner/:ownershipId, with this PR, it will redirect back to /me, which is reasonable)
• [ ] /me/security

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[bot]]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:commit-b39853b22276d126aa90b1eec5341345cc4377fe

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:commit-b39853b22276d126aa90b1eec5341345cc4377fe&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 (~70 bytes added 📈 [gzipped])

``` name parsed_size gzip_size entry-stepper +2491 B (+0.1%) +70 B (+0.0%) entry-main +2491 B (+0.1%) +67 B (+0.0%) ``` Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used.

Sections (~4373 bytes removed 📉 [gzipped])

``` name parsed_size gzip_size reader +80 B (+0.0%) +107 B (+0.0%) me +37 B (+0.0%) +12 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.