Prevent requesting the checklist when the launchpad is displayed

[valterlorran]

Closes #87955

Proposed Changes

• The checklist endpoint is being called even when the Launchpad is displayed. The checklist endpoint should be invoked only when we display the Checklist.
• This PR moves the query to a new wrapper of the SiteSetupList component.

Testing Instructions

• Use the calypso.live link or apply this PR to your local environment.
• Sandbox the public-api.
• Edit the file wp-content/lib/home/views.php and make the maybe_enable_launchpad_legacy_site_setup function always return the views:

function maybe_enable_launchpad_legacy_site_setup( $views ) {
    return $views;
}

• Create a new site through the /setup/free flow
• Launch your site once you reach the fullscreen Launchpad step
• You should land at the Customer Home. Click on the "Show site setup" button on the banner.
• Make sure you see the Checklist and that it works properly.
• Now, undo the changes in wp-content/lib/home/views.php file.
• Refresh the Customer Home page and confirm that /checklist endpoint is not called anymore and you see the launchpad.

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 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:commit-f85aa6ad35993407fb2ff3bd02caae82728d1e9a

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[matticbot]

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

Sections (~31 bytes added 📈 [gzipped])

name  parsed_size           gzip_size
home        +87 B  (+0.0%)      +31 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.

[sixhours]

Looks good! 👍