Adds two GitHub Actions workflows that compile a small smoke test
across all supported ESP32-family SoCs:
* ArduinoBuild.yml: arduino-cli matrix
- Espressif core 2.0.17 / 3.1.1 (esp32, s3, c3, c6, p4, h2)
- M5Stack core 2.1.4 / 3.2.5 (m5stack_core, m5stack_cores3)
* IDFBuild.yml: ESP-IDF v5.1.6 / v5.3 container matrix
- esp32, s3, c3, c6, h2, p4
The smoke test (examples/Test/build_test/) exercises the main M5Unified
APIs (Display, Speaker, Mic, Imu, Touch, Button, Power, Rtc, Log) so
a missing-symbol regression on any target shows up as a build failure.
The M5GFX dependency is fetched at run time:
* Branch: same name as the operation target (master -> master,
everything else -> develop).
* Repo: prefer the same owner's fork (e.g. ainyan03/M5GFX when
running on ainyan03/M5Unified), fall back to upstream m5stack/M5GFX
if the same-name branch is missing in the fork.
This lets the workflow validate "fork develop x fork develop" while
still working unchanged on the upstream m5stack/M5Unified repo.