Add raspberry pi checks to the CI

[sirknightj]

Issue #, if available:

• N/A

Description of changes:
This pull request introduces a new CI/CD pipeline for building and testing our application on ARM-based Raspberry Pi OS environments. The implementation leverages GitHub Actions and QEMU emulation to ensure compatibility and maintain build integrity across different Raspberry Pi OS versions.

Key Features:

1. Utilize QEMU emulation of ARM architecture on x86_64 GitHub runners. (Note: GitHub actions does not currently support linux-arm64)
2. Matrix build strategy: Simultaneously tests on both Debian 11 (Bullseye) and Debian 12 (Bookworm) Raspberry Pi OS versions.
3. Runs the sample GStreamer pipeline test with a 30-second timeout and appropriate error handling.

Security Considerations:

• Environment variable secrets are automatically obfuscated by GitHub actions to prevent accidental logging.

Testing:

• Verified successful building of the project and execution of the GStreamer pipeline (review the logging output of the runners).
• Confirmed proper handling of timeouts and exit codes.
• Checked the logs to confirm that aarch64-linux is indeed being used and not x86_84
  • The images have OpenSSL 1.1.1w and 3.0.15 installed respectively.

This implementation significantly enhances our ability to ensure code quality (reduce build issues) and compatibility across different Raspberry Pi OS versions, reducing manual effort required. Streamlining our development and deployment processes for ARM-based environments.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[unicornss]

Not immediately required for this CR but is something to consider for the future: It would be worth checking if we remove the toolchain after the build has completed successfully.