Dashboard v2: Fix Add new site because the help center store is not ready

[arthur791004]

Part of #103937

Proposed Changes

• Fixes the issue introduced in #103937 where "Add New Site" on Dashboard v2 fails due to the Help Center store not being initialized..

Why are these changes being made?

• The "Add new site" button is broken

Testing Instructions

• Go to /v2
• Click "Add new site" button
• Ensure you can see the modal

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)?

[matticbot]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-147277

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• help-center
• notifications
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug fix/dashboard-v2-create-site on your sandbox.

[matticbot]

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

Sections (~61 bytes added 📈 [gzipped])

name                parsed_size           gzip_size
staging-site             +102 B  (+0.0%)      +61 B  (+0.0%)
sites-dashboard          +102 B  (+0.0%)      +61 B  (+0.0%)
site-settings            +102 B  (+0.0%)      +61 B  (+0.0%)
site-performance         +102 B  (+0.0%)      +61 B  (+0.0%)
site-monitoring          +102 B  (+0.0%)      +61 B  (+0.0%)
site-logs                +102 B  (+0.0%)      +61 B  (+0.0%)
plans                    +102 B  (+0.0%)      +61 B  (+0.0%)
overview                 +102 B  (+0.0%)      +61 B  (+0.0%)
hosting                  +102 B  (+0.0%)      +61 B  (+0.0%)
github-deployments       +102 B  (+0.0%)      +61 B  (+0.0%)
domains                  +102 B  (+0.0%)      +61 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.

Async-loaded Components (~3209 bytes added 📈 [gzipped])

name                                             parsed_size             gzip_size
async-load-calypso-dashboard-sites-add-new-site      +8467 B  (+116.7%)    +3209 B  (+119.3%)

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

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.

[taipeicoder]

Tested and the issue is fixed 👍