Switch from flit to hatchling build system

[garrison]

This switches from flit_core to hatchling for the build system. Likewise, it uses hatch rather than flit in the release.yml workflow.

The primary goal here is to enable progress on

• Shorten top-level module names #221

I have not tested the release workflow against the test pypi instance, but everything looks right to me. If it fails when we do the 0.3.0 release, I am happy to debug.

[coveralls]

Pull Request Test Coverage Report for Build 5149028494

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 89.367%

---

Totals
Change from base Build 5146966568:	0.0%
Covered Lines:	2328
Relevant Lines:	2605

---

💛 - Coveralls

[caleb-johnson]

#235

Sounds great, I opened up an issue to test against the pypi test server ahead of 0.3.0 release day. I'll try to play with this in the next couple weeks

[garrison]

I opened up an issue to test against the pypi test server ahead of 0.3.0 release day. I'll try to play with this in the next couple weeks

Thanks, that'd be awesome :)