Use meson build in place of numpy distutils

[jcapriot]

Switches from a numpy.distutils based build to a meson-python based build.

A few things to note:
Right now it uses pkg-config to find the necessary mkl dependency, of which there are several options for linking against:

• mkl-dynamic-ilp64-seq
• mkl-dynamic-ilp64-iomp
• mkl-dynamic-ilp64-tbb
• mkl-dynamic-lp64-seq
• mkl-dynamic-lp64-iomp
• mkl-dynamic-lp64-tbb
• mkl-sdl

All of which have pkg-config files installed when getting the mkl-devel package from conda. By default it will try to link against the more specific versions if available, and if not default to the sdl package (which I was personally having issues with on my windows machine for some reason).

I would still like to add in an option for specifying the necessary location using an mkl-root option that will supply an option as a fall back in case of no pkg-config.

[codecov]

Codecov Report

Attention: Patch coverage is 8.82353% with 31 lines in your changes are missing coverage. Please review.

Project coverage is 41.06%. Comparing base (c48ea7e) to head (953be5e).

Files	Patch %	Lines
pydiso/mkl_solver.pyx	0.00%	28 Missing ⚠️
pydiso/__init__.py	50.00%	3 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##             main      #12       +/-   ##
===========================================
- Coverage   74.78%   41.06%   -33.73%     
===========================================
  Files           2        3        +1     
  Lines         238      358      +120     
  Branches        0       18       +18     
===========================================
- Hits          178      147       -31     
- Misses         60      209      +149     
- Partials        0        2        +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jcapriot]

Still not quite sure what to do about code-coverage, but in the grand-scheme of things don't think it's that important.

Also note, I've been having segfault issues on windows when linking against the 2024 MKL, so I've added a job to the actions to just keep an eye on it when intel eventually releases an update (or I can get more information about why it might be segfaulting)