Dedicated tester boards for GPIO/I2C/SPI + GPIO CI/CD tests

[omeh-a]

Currently we are unable to test GPIO drivers easily as we don't have a way to systemically coordinate pinmuxing to connect pins internally OR any suitable Maaxboards set up to test hardware. Currently we test I2C and similar protocols on Meson only by using a dedicated board in the testing infrastructure with external hardware.

We should:

1. Set up a similar Maaxboard
2. Change our machine queue setup to separate the electrical test boards from the existing tester pools / possibly seL4 CI path AND we should clearly name these tester boards as such, rather than arbitrarily being something like odroidc4_1.

@alzer89 @midnightveil thoughts would be appreciated :)

[JDuchniewicz]

I think this is quite important. The CI changes would be just making the GPIO test be ran on a different board pool and current infrastructure supports that already. I believe that we should be testing all drivers/components we have for the systems and even having 2-3 boards that would be dedicated to only HW testing would be great.