Multiple ESP32 targets - the future for the Espruino Build structure

pS I'm not suggesting G we go back to the Espruino tools approach.

You mean what we do for ESP32 by pulling a single file out of https://github.com/espruino/EspruinoBuildTools and decompressing it?

Personally I feel like that might still be a good approach - it makes the build time a lot faster and does allow us complete control of the IDF.

As an example, on the current master:

• ESP32 (https://github.com/espruino/Espruino/actions/runs/10768636543/job/29858166005) - 27 sec
  
• ESP32C3 (https://github.com/espruino/Espruino/actions/runs/10768636543/job/29858169688) - 3m42s
  
  

If GitHub ever start making Open Source projects pay for build time that's going to start to be an issue.

(I know that build time of the C3 would never get down to 30s as the ESP32 build seems to be partially built already, but I imagine the GitHub download is a nontrivial amount of that)