Premium Analytics: remove obsolete widget-picker preview aspect-ratio hack

[chihsuan]

Fixes #

Proposed changes

Premium Analytics widgets shipped a per-widget CSS workaround for the widget-picker preview:

:global([inert]:not([inert="true"])) .root {
  height: auto;
  aspect-ratio: 4 / 3;
  overflow: hidden;
}

Why: The picker rendered each widget tile inert, and the preview wrapper's height: 125% of an auto-height parent left height: 100% on .root resolving to auto — so the tile collapsed. The 4:3 aspect-ratio rule gave it a sensible fallback shape.

How: #50271 updated the widget-picker host so it sizes preview tiles itself, so the workaround is now dead code. This PR:

• Removes the aspect-ratio rule from every widget that carried it (16 style modules).
• Removes the matching "Widget picker preview" guidance from the package AGENTS.md so new widgets don't reintroduce it.

What is intentionally kept: the separate :global([inert]) … .leaderboardImage / .avatar / img rules in locations, authors, subscribers-list, and visitors-by-location. Those counter the picker grid's img { object-fit: cover } blowing flags/avatars up to fill the tile — an unrelated concern that #50271 did not touch.

Related product discussion/links

• Follow-up to Premium Analytics: update widget packages and promote in-body controls to widget attributes #50271.

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

No.

Testing instructions

• Build the package (jetpack build --deps packages/premium-analytics) or run Storybook.
• Open the Premium Analytics dashboard's widget picker.
• Confirm every widget preview tile still renders at a sensible size (no collapse, no full-bleed stretch).
• Confirm Locations/Visitors-by-Location flag images and Authors/Subscribers avatars still render at their intended small size in the picker preview (not stretched to fill the tile).

[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