Reasoning for/possibly change HIL test GPIOs for esp32c3

[wisp3rwind]

I just ran some HIL tests locally on the esp32c3 Rust board. According to hil-test/README.md that's the same board that's also used for test runners.

The HIL tests expect GPIO2 and GPIO3 to be connected: However, GPIO2 is connected to the WS2812 LED, which easily interprets whatever you do on that GPIO as "light up at close-to-full brightness", which in turn is somewhat inconvenient if the board happens to sit on your desk and the LED shines at your face.

Thus, I was wondering whether there's a particular reason to use that GPIO? Locally, I just replaced GPIO2 -> GPIO6 in hil-test/src/lib.rs and connected those two pins, which seems to work. Would it also be an option to do that upstream? Of course, I could just apply that change myself whenever I want to test something, but it would be slightly more convenient if I didn't need to.

[bugadani]

@playfulFence can we add this to the list? Accidentally blinding people isn't one of the project goals, we should probably look through all the devkits and avoid driving the LED if we can.