Add Build Workflow

[nstarman]

Workflows for publishing.

PR Checklist

• [ ] Give a detailed description of the PR above.
• [ ] Document changes in the CHANGES.rst file. See existing changelog for examples.
• [ ] Add tests, if applicable, to ensure code coverage never decreases.
• [ ] Make sure the docs are up to date, if applicable, particularly the docstrings and RST files in docs folder.
• [ ] Ensure linear history by rebasing, when requested by the maintainer.

[codecov-commenter]

Codecov Report

Merging #58 (2376d44) into main (86ecfd7) will not change coverage. The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@           Coverage Diff           @@
##             main      #58   +/-   ##
=======================================
  Coverage   80.62%   80.62%           
=======================================
  Files          13       13           
  Lines         449      449           
=======================================
  Hits          362      362           
  Misses         87       87           

[nstarman]

@ntessore, does this look good? There's a mild duplication in the release CI b/c I anticipate we will want to compile not just pure python wheels in the future, so we start with tests then publishing.

[ntessore]

I would prefer starting with a pure Python build and upload to PyPI only. There are a number of ways to publish conda packages, and I would like to give this some thought first.

But if care deeply about using this workflow, that's fine with me, too.

[nstarman]

This is definitely not a hill I want to die on. My preference for this workflow is that I do not want to spend time / effort / thought on building and publishing.

[nstarman]

For now I can just turn off the Conda upload section.

[nstarman]

Done.