Sidebar: relabel WooCommerce to Store setup for eCommerce plans

[bogiii]

Part of DOTCOM-17755

Proposed Changes

• Relabel the WooCommerce sidebar entry to "Store setup" for eCommerce-plan sites in the WordPress.com (dotcom) context.
• Add relabelWooCommerceAsStoreSetup util that rewrites the item title, matching both the admin-menu API slug (woocommerce) and the static fallback slug (woo-php).
• Wire the util into useSiteMenuItems, gated on isEcommercePlan(planSlug).
• Add unit tests for the util.

Why are these changes being made?

On eCommerce-plan sites the WooCommerce entry is really the store-setup destination, so "Store setup" is clearer than "WooCommerce". The change is scoped to the dotcom context because only WordPress.com plans carry the eCommerce plan slug, and Jetpack self-hosted sites resolve their menu through an earlier branch.

Testing Instructions

• On an eCommerce-plan WordPress.com site, open the site sidebar and confirm the WooCommerce entry reads "Store setup".
• On a non-eCommerce plan (e.g. Business), confirm the entry still reads "WooCommerce".
• Run yarn test-client client/my-sites/sidebar/utils/test/relabel-woocommerce-store-setup.ts.

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?
• For UI changes, have you tested the affected components in dark mode?
• Have you tested accessibility for your changes? Ensure the feature remains usable with various user agents (e.g., browsers), interfaces (e.g., keyboard navigation), and assistive technologies (e.g., screen readers) (PCYsg-S3g-p2).
• Have you used memoizing on expensive computations?
• 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)?
• 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)?

🤖 Generated with Claude Code

[github-actions]

Calypso Live (direct link)

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

Jetpack Cloud Live (direct link)

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

Automattic for Agencies Live (direct link)

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

Dashboard Live (dotcom) (direct link)

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

Dashboard Live (A4A) (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-186120&env=dashboard-a4a

[markbiek]

LGTM!