Premium Analytics: port the Bookings by device widget

[nerrad]

Fixes: WOOA7S-1463

Proposed changes

• Ports the Bookings by device widget into the Premium Analytics customizable dashboard.
• Registers the jpa/bookings-by-device widget and renders the shared bookings-by-device widget inside WidgetRoot using dashboard-level report params.
• Ensures booking product filters are forwarded through useReportOrderAttribution() so the widget uses the product-filtered order-attribution endpoint.
• Adds regression coverage for the hook-level product filter forwarding and product-filtered order-attribution query path.
• Adds Storybook mock coverage for booking-filtered order-attribution-by-product device data.
• Adds standalone Default and WithComparison stories plus a real-dashboard WidgetDashboardWithWidget story for the widget.

Storybook screenshot

Captured from the local Storybook widget dashboard story.

Related product discussion/links

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

• git diff --check origin/trunk...HEAD
• CI=true /Users/dethier/Library/pnpm/pnpm --filter @automattic/jetpack-premium-analytics test -- use-report-order-attribution
• CI=true /Users/dethier/Library/pnpm/pnpm --filter @automattic/jetpack-premium-analytics typecheck
• CI=true /Users/dethier/Library/pnpm/pnpm --filter @automattic/jetpack-premium-analytics build
• CI=true /Users/dethier/Library/pnpm/pnpm --filter @automattic/jetpack-storybook storybook:build
• Verified the built Storybook iframe packages-premium-analytics-widgets-bookingsbydevice--widget-dashboard-with-widget in the browser: title rendered, Desktop/Mobile/Tablet labels rendered, chart elements rendered, and no visible Storybook render error appeared.

[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

[chihsuan]

Solid port, verified the story renders the device breakdown end-to-end! 👍

Left a few inline notes worth a look before merge.

[nerrad]

Opened draft follow-up PR #50031 as an example path for making jpa/bookings-by-device conditionally available only when WooCommerce Bookings is installed and active: #50031