Self-service site restore: remove second sites query for deleted sites

[mpkelly]

Related to #89997 (comment)

Proposed Changes

• Don't do a separate query for deleted sites and merge them with active sites when the user requests "all". Instead, update the backend to return deleted sites with all sites (see D147075-code)

Testing Instructions

• Make sure you have some deleted sites that are visible on the trunk when filtering to the status "deleted". Note the slugs.
• Apply D147075-code
• Apply patch Site Restore: Add is_deleted attribute to sites api response to flag deleted sites jetpack#37142 to your sandbox
• Test this on Calypso Live or local branch
• You can find your deleted sites when filtering to "all" now because of D147075-code
• You can also filter to "deleted" and see only your deleted sites
• You should not see deleted sites on the /setup/migrate-hosted-site and /setup/import-focused flows.

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• https://wpcalypso.wordpress.com/devdocs/docs/testing/index.md 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-106013

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-106013&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 (~42 bytes removed 📉 [gzipped])

name           parsed_size           gzip_size
entry-stepper        -83 B  (-0.0%)      -42 B  (-0.0%)
entry-main           -83 B  (-0.0%)      -42 B  (-0.0%)
entry-login          -83 B  (-0.0%)      -42 B  (-0.0%)

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

Sections (~40 bytes removed 📉 [gzipped])

name                     parsed_size           gzip_size
sites-dashboard               -156 B  (-0.0%)      -33 B  (-0.0%)
site-monitoring               -156 B  (-0.0%)      -33 B  (-0.0%)
hosting                       -156 B  (-0.0%)      -33 B  (-0.0%)
github-deployments            -156 B  (-0.0%)      -33 B  (-0.0%)
import-hosted-site-flow        -63 B  (-0.0%)      -18 B  (-0.0%)
import-flow                    -46 B  (-0.0%)       -7 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

• blaze-dashboard
• command-palette-wp-admin
• odyssey-stats

To test WordPress.com changes, run install-plugin.sh $pluginSlug update/change-deleted-state-filter-logic on your sandbox.

[vykes-mac]

Ready to merge once the jetpack changes are on WPCOM. I already merge that PR