Add tests for circuitpython-build-bundles

[Neradoc]

Add tests to the PR build workflow in order to catch errors and malformed bundles.

[jepler]

There's currently a "test" in Actions, but it only checks that the build process exits with a zero status. However, due to some recent issues it appears that we need to check something about the actual content of the .mpy files that are generated.

[jepler]

@FoamyGuy do you have any interest in grabbing this?

[FoamyGuy]

I'll add this to my list to look into. It's got a few things ahead of it so it may be a little bit.

@jepler or @Neradoc do either you have an idea in mind for what kind of validation we'd want to do on the mpy file? The only that come to mind for me are check that the size isn't 0, and maybe try importing it under the unix port though I don't know if that will be possible for every library.

[2bndy5]

I think the scope of this project is simply to create a distribute-able bundle for any given package(s).
Thus, it makes sense to verify the zip file's file/folder structure and the __version__ is modified as expected.

maybe try importing it under the unix port though I don't know if that will be possible for every library.

This seems like it is specific to testing mpy by itself. I think the extent of mpy tests in the scope of this project is:

• If the mpy binary is downloaded from AWS, then ensure it doesn't seg fault (when given a hello_world.py script) and corresponds to the expected circuitpython version.
• If mpy is built from source (Linux-specific, legacy behavior prior to circuitpython v5 or whenever the circuitpython repo started uploading pre-built mpy binaries to AWS), then just ensure the build completes successfully and it doesn't seg fault when given a hello_world.py script.

Any other mpy tests/concerns should be satisfied before uploading the binary to AWS.