Premium Analytics: port the Sales by UTM source widget

[nerrad]

Fixes: WOOA7S-1481

Proposed changes

• Ports the Sales by UTM source widget into the Premium Analytics customizable dashboard.
• Registers the jpa/sales-by-utm-source widget and renders the shared sales by UTM widget inside WidgetRoot for the source view using dashboard-level report params.
• Forwards dashboard error state through WidgetRoot so report failures surface through the host error UI.
• Adds a Storybook dashboard story for the widget using report mocks.

Storybook screenshot

Captured from the local Storybook widget dashboard story.

Related product discussion/links

• WOOA7S-1481; 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

• /Users/dethier/Library/pnpm/pnpm install --frozen-lockfile
• /Users/dethier/Library/pnpm/pnpm --filter @automattic/charts build
• /Users/dethier/Library/pnpm/pnpm --filter @automattic/number-formatters build
• /Users/dethier/Library/pnpm/pnpm --filter @automattic/jetpack-wp-build-polyfills build
• /Users/dethier/Library/pnpm/pnpm --filter @automattic/jetpack-premium-analytics typecheck
• /Users/dethier/Library/pnpm/pnpm --filter @automattic/jetpack-premium-analytics build
• /Users/dethier/Library/pnpm/pnpm --filter @automattic/jetpack-storybook storybook:build
• Browser smoke against the built Storybook iframe for packages-premium-analytics-widgets-salesbyutmsource--widget-dashboard-with-widget: verified the widget title/region, mocked source rows (google, facebook, instagram), values, comparison legend, SVG chart rendering, and no NaN/undefined. The only console error observed was the known baseline duplicate core/notices registration.

[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