Allow overriding CIRCUITPY_BLEIO on 4MB espressif boards

[Neradoc]

While we are waiting for CP 10, this allows overwriting CIRCUITPY_BLEIO on 4MB espressif boards from the make command, or with the github custom build action on a fork. It it is then possible to make space for _bleio by disabling other modules.
Or by using the no-ota-no-uf2 partition scheme. Note that the no-ota with uf2 build won't work with the current versions of tinyuf2 (pending adafruit/tinyuf2#432) so this requires installing via the bin anyway (or a custom tinyuf2 while you're at it).

For example:

make BOARD=adafruit_qtpy_esp32s3_4mbflash_2mbpsram CIRCUITPY_BLEIO=1 \
FLASH_SIZE_SDKCONFIG=esp-idf-config/sdkconfig-flash-4MB-no-ota-no-uf2.defaults

esptool.py --port $PORT --after=no_reset erase_flash
esptool.py --port $PORT write_flash 0x0000 build-adafruit_qtpy_esp32s3_4mbflash_2mbpsram/firmware.bin

Note that you can also preserve the drive when erasing. (It does erase NVM)
These values are for the 4MB-no-ota-no-uf2 partition scheme.

esptool.py --port $PORT --after=no_reset erase_region 0 0x210000

[dhalbert]

I think is a good idea, even if it is temporary, because it makes it easier to enable BLE now on these boards.

[tannewt]

Fine with me too!

[henrygab]

or with the github custom build action on a fork

I have never built CircuitPython locally, and I would prefer to avoid setting up and validating a custom build environment just for this purpose. Thus, I'm excited to use GitHub actions.

@Neradoc ... I'd like to try this. Presume that I have already:

• created various github actions in the past
• forked this repository, and
• enabled github actions in my fork of circuitpython
• want to enable this for an ESP32-S3 board with 4MB flash and 8MB PSRAM (specifically, the reverseTFT feather)

Could you give a few more details on the changes needed to enable this custom build action for that fork? (Or, if you already have this fork yourself, can you point to it?)

thank you!

[Neradoc]

The custom build action is currently broken, see #10117
This is how you start it (to do in you fork) - but currently results in an error.

If you understand github actions, you can try to fix the issue in your fork (and make a PR when it works !)