Premium Analytics: wire existing Stats sanitizers

[kangzj]

Fixes #

Proposed changes

• Wire the existing Stats time-series, visits, email summary, and email breakdown sanitizers into the shared stats query sanitizer map.
• Export the existing email stats item types from the Premium Analytics data package root.
• Add query coverage so every current stats sanitizer key is accepted by statsProxyQuery.

Related product discussion/links

• Follow-up split from Premium Analytics: normalize secondary Stats reports #49780.

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

No.

Testing instructions

• Run CI=true jp pnpm --dir projects/packages/premium-analytics test -- packages/data/src/queries/__tests__/stats-queries.test.ts packages/data/src/processing/stats
• Run CI=true jp pnpm --dir projects/packages/premium-analytics typecheck

[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