ESP32: support dynamic freq scaling and wifi power save - #5473

AN issue I just discovered: the following loop in uselect busy-waits: https://github.com/micropython/micropython/blob/master/extmod/moduselect.c#L250-L257. I'll throw a ulTaskNotifyTake(pdFALSE, 1); in there to see what happens...

Edit: also https://github.com/micropython/micropython/blob/master/extmod/moduselect.c#L176

Well, this last commit fixed asyncio. But now I better profess that I have no friggin' clue about what I'm doing, LOL :-)

rebased on master and squashed commits

I'd like to mention, that as per the esp-idf documentation, it is possible to keep some peripherals, including UART, functioning properly during auto-lightsleep (specifically frequency scaling), by using "REF_TICK" as a tick source. That would make this feature far more usable and desirable.

I think the WLAN.connect.(..., listen_interval) addition is great, definitely useful and even necessary for some applications.

The dynamic frequency scaling is also good but I think it's not yet clear how to make it work properly. And the changes here (like changing the UART clock source) seem like they could have unintended affects on existing behaviour. Also newer version of the IDF (since v4.1) have changed how this is configured.

So I suggest to split out the addition of listen_interval and merge just that feature.

What if auto lightsleep was something you manually enabled and disabled? Lots of applications don't need to do anything besides listen for commands, most of the time, you could just manually come out of that state when needed.

This is an automated heads-up that we've just merged a Pull Request
that removes the STATIC macro from MicroPython's C API.

See #13763

A search suggests this PR might apply the STATIC macro to some C code. If it
does, then next time you rebase the PR (or merge from master) then you should
please replace all the STATIC keywords with static.

Although this is an automated message, feel free to @-reply to me directly if
you have any questions about this.

Closing due to inactivity. Also this probably won't work with IDF 5.x.

(Still, it would be great to have the listen_interval feature per #5473 (comment), if someone wants to implement just that bit, feel free to open another PR.)