Add ASan/UBSan CI job and clang-tidy/cppcheck CI job

[OldCrow]

Summary

Runtime sanitizers (ASan, UBSan) and static analysis (clang-tidy, cppcheck) are not part of CI. They are only run manually. Undefined behavior or out-of-bounds issues could be introduced without automated detection.

Action needed

ASan / UBSan CI job

1. Add a new CI job (e.g., sanitizers) in .github/workflows/ci.yml.
2. Build libew, ewpresenter, and tests with -fsanitize=address,undefined (GCC/Clang) on Linux.
3. Run ctest under the sanitizer-instrumented build; fail the job on any sanitizer report.

clang-tidy / cppcheck CI job

1. Add a static-analysis job.
2. Run clang-tidy against libew and ewpresenter using the existing .clang-tidy config.
3. Run cppcheck on the same sources.
4. Fail the job on any new warning or error not already suppressed.

Both jobs can be in the same workflow file; keep them as separate jobs so they run in parallel and failures are identifiable independently.

Files

• .github/workflows/ci.yml — add new jobs
• .clang-tidy — already present; review suppression list before wiring to CI