Use github workflow to build sdist/wheel and upload.

[Carreau]

Setup a github workflow based on numcodec to build sdist and wheel. Adapted from numcodec.
I have to check what ciwheel do, as zarr wheels are likely universal and dont' need to be per-platform

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/tutorial.rst
• Changes documented in docs/release.rst
• AppVeyor and Travis CI passes
• Test coverage is 100% (Coveralls passes)

[Carreau]

I switched from cibuildwheel to "build" which is a non-official pep518 packed (hence adding the Pyproject.toml file as well).

[jakirkham]

Do we need to do anything special to indicate the wheel is not architecture dependent?

[Carreau]

Do we need to do anything special to indicate the wheel is not architecture dependent?

not as far as I can tell, I think that's one of the main difference between build and cibuildwheel.
on a non-tagged repository I get

$ ls -1 dist/
zarr-2.4.1.dev69+dirty-py3-none-any.whl
zarr-2.4.1.dev69+dirty.tar.gz

Indicating the wheel is compatible all platforms.

[Carreau]

Currently testing on myfork [https://github.com/Carreau/zarr-python/actions], the action does not work correctly yet.

[jakirkham]

Thanks Matthias! 😄