Premium Analytics: port the Bookings revenue by customer type widget

[nerrad]

Fixes: WOOA7S-1465

Proposed changes

• Ports the Bookings revenue by customer type widget into the Premium Analytics customizable dashboard.
• Registers the jpa/bookings-revenue-by-customer-type widget and renders the shared bookings revenue by customer type widget inside WidgetRoot using dashboard-level report params.
• Adds standalone Storybook stories for the default and comparison states, plus a dashboard-hosted Storybook story using the shared WidgetDashboardWithWidget helper.
• Keeps this branch rebased onto trunk; the shared dashboard/package scaffolding is already provided by trunk, so this PR diff is limited to the widget port.

Storybook screenshot

Captured from the local Storybook widget dashboard story.

Related product discussion/links

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

Using pnpm 11.5.2:

• pnpm install --frozen-lockfile
• pnpm --filter @automattic/charts build
• pnpm --filter @automattic/number-formatters build
• pnpm --filter @automattic/jetpack-wp-build-polyfills build
• pnpm --filter @automattic/jetpack-premium-analytics typecheck
• pnpm --filter @automattic/jetpack-premium-analytics build
• pnpm --filter @automattic/jetpack-storybook storybook:build
• Verified the built Storybook iframe packages-premium-analytics-widgets-bookingsrevenuebycustomertype--widget-dashboard-with-widget: title rendered, chart labels Returning and New rendered, and no NaN/undefined text. The only console error was the existing Storybook core/notices duplicate-registration message.

[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

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