Add initial HIL testing

[SergioGasquez]

Add HIL CI that:

• In Ubuntu runners, build esp-hal hello_world example for every target, upload artifacts to actions
  • In Ubuntu runner, build espflash, upload artifacts to actions
  • In self-hosted runners, run the HIL tests:
    • Run board-info, checks that "esp32" is printed
    • Run flash, checks that "Flashing has completed!" is printed
    • Run monitor for 5secs, checks that "Hello world!" is printed
    • Run erase-flash, checks that "Flash has been erased!" is printed
    • Run read-flash, checks that "Flash content successfully read and written to" is printed
    • Use hexdump to verify that read flash is empty (its been erased, so it should be)
    • Run save-image, checks that "Image successfully saved!" is printed
    • Run write-bin, checks that "Binary successfully written to flash!" is printed
    • Run monitor for 5secs, checks that "Hello world!" is printed
  • Add info! logs for when the command ends successfully
  • Add a non-interactive flag to monitoring so it can be used in CI
  • Add an app binary for every target under resources folder. Apps where generated with esp-template (rev: 905de42)default settings

HIL CI errors:

• ESP32 is failing when trying to flash the board, not sure what is happening there.
• ESP32-C2 seems to be offline.
• ESP32-C3 fails as its a rust board and it cant read the uart.
• ESP32-C2 cant monitor. Its a 26MHz C2 and it only reads noise

We would also need to decide when this action runs

Thanks to @achxkloel for the investigation on the monitoring issue

[SergioGasquez]

HIL CI is now green! Only CI on macos is failing due to: https://github.com/esp-rs/espflash/issues/597. The only thing left would be to decide when the HIL CI should run.