MATTER-5224: Implement automated generation of metadata with hwfilter

[Michael Duggan (miduggan24)]

Issue Link:
MATTER-5224

Description of Problem/Feature:
Need standardized way to generate all metadata files

Description of Fix/Solution:
Implement the following to automatically generate matter_templates.xml, matter_demos.xml, and new board_compatibility_matrix.html to help with manual work of updating confluence with matrix

• Add tags to each app slcp file to filter only supported boards for each app
• Implement generate_metadata_hwfilter.py script to generate metadata files by cloning hwfilter locally and running with latest sisdk and wiseconnect packages to pick up boards and devices
• Introduce hwfilter-config.yml as high-level board and device filtering for hwfilter to apply to all apps
• Introduce metadata-generation.yml to handle demo variants built in CI, exclusions from templates and demos files, hard-coded board lists for special cases, and using boards from CI for demos for certain apps
• Introduce template jinja template files to populate templates and demos xml files correctly
• Implement CI check to validate that all exposed demos are covered in CI
• Remove --output_suffix from trustzone builds (not needed anymore, trustzone within app name)
• Remove untested wifi boards from templates xml file

Testing Done:

• Manual verification of generated templates and demos xml files
• Run demo validation script locally
• AI-assisted validation of generated xml files
• Stage extension, load into studio, verify apps and demos are present and functioning
  • Note that demos are present but not yet functioning, this is because newly named demo artifacts are not yet present in artifactory

---

Note

Medium Risk
Medium risk because it changes CI validation and adjusts TrustZone build arguments, which could cause builds or metadata checks to start failing if expectations differ. The large generated board_compatibility_matrix.html is low functional risk but adds repository noise/size.

Overview
Metadata validation is expanded in CI and TrustZone build args are simplified.

The MG24 TrustZone CI config drops --output_suffix trustzone from .github/silabs-builds-mg24-trustzone.json, relying on naming/other mechanisms for TrustZone identification.

The validate-metadata GitHub Actions workflow adds a new validate-demo-images job that runs slc/script/validate_demo_images.py to ensure matter_demos.xml demo image URIs map to existing .slcw solutions and are covered by the appropriate CI board JSONs.

A generated board_compatibility_matrix.html is added to the repo, providing an example-vs-board compatibility matrix for reference/documentation.

^{Reviewed by Cursor Bugbot for commit d4da968. Bugbot is set up for automated code reviews on this repo. Configure here.}

[Michael Duggan (miduggan24)]

bugbot run

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 384c32b. Configure here.}