Solution group pages: layout 22 + Template-06 workbook import

- new frontend layout 22 "Solution Group Page" (provider LAYOUT_MAP,
  TCA layout item, locallang_pages.xlf; zones hero=colPos1, main=colPos0
  like layout 5 so the front end reuses its components)
- new pipeline Import\SolutionGroupPageImporter +
  vitec:import-solution-group-workbooks (inbox
  migrations/solutiongroups_xlsx_in/, gitignored): reads the agency
  "Template 06" group workbooks by column-A label scan, resolves the
  group via "Hero H1" -> is_group record -> detail_page (pages must
  exist), cursor-based slotNext() allows repeated CTypes per column
- element plan per page: markethero (+#capabilities CTA anchor) + hero
  intro paragraph; intro + supporting 50/50; challenges header + 4
  text_only cards; capabilities header + 4 alternating horizontal cards
  (bullets as <ul>); usecaselist shipped HIDDEN (an empty selection
  would list ALL stories - editors pick, then unhide); marketinsights;
  prefooter ctabanner. Page properties as on the sub-solution pages,
  8 curated keyword sets
- 56 numbered grey placeholders for pages 459-466 (7 slots per page)
- applied to all 8 group pages, live-verified on 459/465; the solutions
  branch is now content-complete (groups + 39 details)
- spec v1.24 (revision row, head/footer)

Found on the way: the "Engagament" typo lives in page 465's title AND
slug; the record is spelled correctly. Fix needs coordination with the
sub-solution workbook metas - own task, not done here.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

packages/vitec/Classes/View/BackendLayoutDataProvider.php

@@ -62,6 +62,9 @@ final class BackendLayoutDataProvider implements DataProviderInterface
         19 => ['title' => 'Events Overview',        'zones' => ['hero', 'main']],
         20 => ['title' => 'Contact Page',           'zones' => ['hero', 'main', 'sidebar']],
         21 => ['title' => 'Sub-Market Page',        'zones' => ['smHero', 'smIntro', 'smWorkflow', 'smTestimonials', 'smProducts', 'smInsights']],
+        // Solution group hero pages (Joe's Template 06, import 2026-10-23) -
+        // same hero/main zones as layout 5, so the front end reuses parts.
+        22 => ['title' => 'Solution Group Page',    'zones' => ['hero', 'main']],
     ];
 
     /** Display name for each zone. Shown as column header in the BE page module. */