This wraps the process of building or downloading mpy-cross for a specified
version, then running it with specified arguments.
e.g.,
```
$ circuitpython-mpy-cross --circuitpython-version 9.x -- --version
CircuitPython 9.0.0-alpha.2 on 2023-10-27; mpy-cross emitting mpy v6.1
```
Most often I find that I want to check just one kind of artifact
(e.g., mpy files) and this is a quicker syntax than excluding the
other 3 types with 3 --ignores.
Some bundles, such as circuitpython-fonts, don't use submodules to
contain their individual libraries.
Change build_bundle_json so that it works correctly if multiple
libraries come from the same submodule.
With this change, the generated metadata for circuitpython-fonts
contains an entry for every font, not just for one font.
This is more dependable, and when we know the package name we can
glob inside it to get all files such as bin or ttf files.
This will allow e.g., 5x8.bin & ov5640_autofocus.bin within
bundles.
the behavior of bundlefly and circup when encountering .bin files
needs to be checked.
Tested by building modified pycamera bundle and the autofocus.bin file
appears in the generated zip files:
```
pycamera-py-ec67bde/lib/adafruit_pycamera/ov5640_autofocus.bin 4077 4096
pycamera-8.x-mpy-ec67bde/lib/adafruit_pycamera/ov5640_autofocus.bin 4077 4096
pycamera-9.x-mpy-ec67bde/lib/adafruit_pycamera/ov5640_autofocus.bin 4077 4096
```
There's at least one library in the bundle that has incorrect metadata
and that leads to an error:
https://github.com/adafruit/Adafruit_CircuitPython_Colorsys/pull/29
This is a weird one since some devices have it in core now, and others don't.
This happened in part because I copypasted the list currently in pipkin instead of tweaking the existing list, which was initially added with this module in the list: b9957133a9
The code generates a temp file with the library version.
By mistake that was ALWAYS copied back to the mpy file for single file libraries.
The temporary files for the package libraries were also not deleted.
For windows compatibility, the temporary file must be copied (and therefore erased) outside of the with block. In this PR we only keep the temporary file open the time to write to it, and then do the rest.
In Micropython 18 (and CP 7.3.0) there are some language fixes to previous syntax errors in f-strings, and maybe others.
A string like this would not compile prior to 7.3.0:
```py
string = "123456789"
print(f"{string[2:6]}")
```
Note that an MPY file with that code generated with mpy-cross 7.3.0 runs properly on 7.0.0 according to my tests.
