Premium Analytics: add forced Loading/Error/Empty Storybook stories for migrated widgets

[chihsuan]

Proposed changes

• Add forced Loading/Error/Empty Storybook stories for the WidgetState migration in Premium Analytics: migrate widgets to WidgetState for loading/error/empty states #50383.
• Use the shared widget canvas so forced states render like dashboard cards.

Related product discussion/links

• WOOA7S-1675

Does this pull request change what data or activity we track or use?

No.

Testing instructions

• Build Storybook and open Packages > Premium Analytics > Widgets.
• Check a few Loading, Error, and Empty stories, e.g. WordAdsChartTabs, Search terms, and Store performance.
• Confirm Default / WithComparison stories still render populated.

Screen.Recording.2026-07-13.at.5.36.04.PM.mov

[jp-launch-control]

Code Coverage Summary

No summary data is available for parent commit 87dcbb5, so cannot calculate coverage changes. 😴

If that commit is a feature branch rather than a trunk commit, this is expected. Otherwise, this should be updated once coverage for 87dcbb5 is available.

Full summary · PHP report

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!