Premium Analytics: normalize secondary Stats reports

[kangzj]

Fixes #

Proposed changes

• Add split secondary Stats normalizers for devices, archives, publicize, followers, tags, comments, and comment followers.
• Add shared generic-list helpers and endpoint-specific fixture coverage for summarized and raw response shapes.
• Incorporate review/browser feedback: support summarized archives, align video-play summary fixtures with the live plays shape, avoid stringifying object labels as [object Object], and leave UTM unnormalized because it was inspected only for request behavior in this stack.

Related product discussion/links

• Stacked on Premium Analytics: normalize Stats time-series reports #49779.
• Stack continues in Premium Analytics: add remaining Stats hooks #49781.

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

No. This only normalizes existing Stats API response shapes.

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: dashboard and detail-page requests were inspected while logged in. Summarized secondary endpoints use summarize=1; detail and period shortcut requests also continue to use summarize=1, usually with max=0. Authenticated raw replays without summarize=1 confirmed endpoint-specific days buckets such as files, plays, search_terms, clicks, groups, postviews, and authors, plus scalar totals where present.
• UTM was inspected for request behavior only and is intentionally not normalized by this PR.

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