Introducing hatch-meson, a port of meson-python to a set of hatchling plugins

[virtuald]

meson-python is really good at what it does, so why bother with another way to make python packages via meson? Here's what I have in my README:

Why does this exist then?
Meson is great for building native libraries due to its simple, straightforward build syntax. This simplicity is one of its most compelling features, but at the same time can make it impossible to accomplish something that the Meson designers did not intend to make possible.

As a Hatchling build plugin, this project allows you to leverage Meson to handle what it does best, and use other Hatchling plugins for tasks Meson doesn’t support.

When using hatch-meson, it is intended that you only use meson for things that require a build system, and that you use Hatchling features for other aspects of packaging a python project.

Most of the code for hatch-meson and almost all of the current tests are copied directly from meson-python. I have some ideas I'd like to play with and some immediate needs, so it seemed to me that the most expedient way to accomplish those is with a separate project.

I do think that at some point if this stabilizes it may make sense to merge hatch-meson back into meson-python as a subpackage (assuming they were interested in it), but until then I expect to continue pulling in bugfixes and features from meson-python periodically.

Most people shouldn't use this right now (or perhaps ever), but if you're interested in collaborating then please take a look and try it out: https://github.com/virtuald/hatch-meson