Deliberately renames the pimoroni-pico directory so that paths which reference it will break with a compilation error.
This ensures a micropython build works robustly if a user renames/moves the pimoroni-pico directory relative to micropython.
This change submodules in our fork of ulab with an added usermod.cmake and adds it to the top-level usermod.cmake for our shipped modules.
It should - in theory - result in ulab being included in release builds.
* C++ libs/examples workflow
* MicroPython workflow
* Workaround broken MicroPython submodules (http does not support shallow clones)
* Upload .uf2 to releases
* Switch to CI fork of uP for custom config - https://github.com/pimoroni/micropython/tree/continuous-integration