WHL: setup automated wheel builds for Linux

[neutrinoceros]

ref #10
At the time of opening, this is merely copied from a project with a similar setup, but might not work out of the box (in particular, I expect I'll need some find tuning to ensure gfortran is available in all containers), so I'll probably need a couple iterations to get something useful out of it.

[neutrinoceros]

CI might not trigger here for a couple reasons, including the fact that I just added a workflow that isn't present on master. I'll try to iterate with manual runs on my fork.

[neutrinoceros]

for reference here's a log from a sucessful run on my fork: https://github.com/neutrinoceros/dsharp_opac/actions/runs/22630573533/job/65579213543

[neutrinoceros]

Wheels seem surprisingly large at ~9MiB (I would expect the entire code to fit in a 100KiB wheel). I note that almost all of it is contributed by dsharp_opac/data + dsharp_opac/constants, which could likely be distributed as their own data package, though that could be a secondary goal.

[birnstiel]

Thanks. Is there anything for me to do here? I saw the publishing is still commented out. Should I enable that on the PyPI side already?

[neutrinoceros]

If you're already on board with it, sure ! I'll uncomment it.
Here's the docs in case you need it: https://docs.pypi.org/trusted-publishers/

(I was expecting more of a sales pitch to be needed, hence my attempt to separate concerns at first)