Premium Analytics: port the Gross sales over time widget

[nerrad]

Fixes: WOOA7S-1470

Proposed changes

• Ports the Gross sales over time widget into the Premium Analytics customizable dashboard.
• Registers the jpa/gross-sales-over-time widget and renders the shared order metric widget inside WidgetRoot for orders_value_gross using dashboard-level report params.
• Threads the dashboard widget error channel through WidgetRoot using the current trunk widget render prop pattern.
• Adds standalone Storybook Default and WithComparison stories plus a separate WidgetDashboardWithWidget dashboard story with dashboard sizing and date preset controls.
• Warms up the line chart composition in the Storybook story so the static Storybook/Vite build renders the comparative line chart.

Storybook screenshot

Captured from the local Storybook widget dashboard story.

Related product discussion/links

• WOOA7S-1470; parent WOOA7S-1457.
• Follows the widget port structure from Premium Analytics: port the Average items per order widget #49505.

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

No.

Testing instructions

• pnpm --filter @automattic/jetpack-premium-analytics typecheck
• pnpm --filter @automattic/jetpack-premium-analytics build
• pnpm --filter @automattic/jetpack-storybook storybook:build
• Static Storybook iframe smoke for packages-premium-analytics-widgets-grosssalesovertime--widget-dashboard-with-widget: verified the dashboard title, widget title, currency value, chart SVGs, and no NaN or undefined text.

[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!

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report