Adding bindings for MicroPython

[amotl]

Dear @vshymanskyy and @SRGDamia1,

first things first: Thanks for conceiving and maintaining this excellent library!

Recently, I had some thoughts about what it would take to bring TinyGSM to the world of MicroPython. The library API entrypoints would have to be wrapped appropriately in order to interface nicely with the MicroPython API.

Based on that, I've already mentioned this idea within stinos/micropython-wrap#3 - thanks @SRGDamia1 and @stinos for contributing to this discussion already.

Another approach would be to look at Micropython API to any C library! by @amirgon and @embeddedt coming from the Micropython Binding for lvgl (LittlelvGL) which is able to create an automatically generated Micropython module with classes and functions through a little helper program called gen_mpy.py.

While I am humbly improving my C-level skills through things like pycom/pycom-micropython-sigfox#356 or pycom/pycom-micropython-sigfox#368, I believe it takes more to that in comparison to what I currently would be able to contribute code-wise directly.

Nevertheless, I wanted to bring up the idea and leave a note about this here in order to see whether it resonates with you in general and to eventually start a discussion others could join in order to bring this forward.

Thanks already and with kind regards,
Andreas.

P.S.: While I recognize the current architecture is built around enabling only a single, specific hardware module through compile-time constants (#280, #346), I am optionally looking towards a respective integration into MicroPython where hardware support could be selected at runtime. While this definitively won't work out well on memory-constrained MCUs like the AVR series or lower-end ARMs, it would well be an option for ESP32 MCUs and such which offer plenty of memory to add this level of convenience.