fix: narrow the icon-cap rule to filename _110x110 so banner content images render at natural width

My previous .page-body a > img:only-child rule was too broad -- it
also squashed wide content banners on /community (Benefits,
Responsibilities, Expert Feedback / 4-step) down to 110px. Use a
filename-pattern match instead so only the explicitly icon-sized
PNGs (for_users_110x110, citing_us_110x110, etc.) get the
thumbnail cap.

Author: adamjohnwright

projects/website-angular/src/app/page/page.component.scss

@@ -4,14 +4,14 @@
     height: auto;
   }
 
-  // Link-wrapped images on MDX landing pages are icon thumbnails
-  // (e.g. the For Users / For Developers / Citing us modules on
-  // /documentation). The source PNGs are ~459x459 even when their
-  // filename advertises 110x110, so the default max-width: 100%
-  // lets them dominate the page. Cap link-only image children at a
-  // sensible thumbnail size and centre them; legitimately wide
-  // content images (no surrounding link) keep the original behaviour.
-  ::ng-deep a > img:only-child {
+  // Module-icon thumbnails on the landing pages (e.g. the For Users /
+  // For Developers / Citing us modules on /documentation) are authored
+  // with `_110x110` baked into the filename even though the PNG bytes
+  // are ~459x459, so without this rule they dominate the page. Match
+  // on that filename hint so other link-wrapped content images (the
+  // wide Benefits / Responsibilities / collaborate banners on
+  // /community, etc.) keep their natural sizing.
+  ::ng-deep img[src*="_110x110"] {
     display: block;
     max-width: 110px;
     max-height: 110px;