Premium Analytics: add Stats app hooks

[kangzj]

Fixes #

Proposed changes

• Add split Stats app query factories and hooks for app/admin resources: referrers spam, site never-published state, plan usage, dashboard modules, dashboard module settings, purchases, notices, and commercial classification mutation.
• Keep app/admin resources in the stats-app query-key namespace, separate from normalized report hooks.
• Incorporate earlier review feedback: remove the unused app-query enabled knob, re-export StatsAppNoticeMutationParams from the hooks layer, explain the cross-namespace referrers invalidation, document that notices use the local plugin REST route, and invalidate plan usage after commercial-classification changes.

Related product discussion/links

• Stacked on Premium Analytics: add remaining Stats hooks #49781.

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

No. This adds hooks for existing app/admin resources and mutations.

Testing instructions

• Run pnpm --dir projects/packages/premium-analytics test --runInBand.
• Run pnpm --dir projects/packages/premium-analytics typecheck.
• Run pnpm --dir projects/packages/premium-analytics build.
• Browser verification for the stack: the live Stats dashboard was inspected while logged in to validate request behavior for dashboard cards, detail pages, period shortcuts, summarized requests, and raw authenticated replays without summarize=1.

[jp-launch-control]

Code Coverage Summary

No summary data is available for parent commit 34c4485, so cannot calculate coverage changes. 😴

If that commit is a feature branch rather than a trunk commit, this is expected. Otherwise, this should be updated once coverage for 34c4485 is available.

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!