chore: include cuda kernel tests in sdist

[agoose77]

Hatchling ignores anything that is ignored by the VCS by default. We can use artefacts to explicitly include e.g. the generated CUDA kernel tests.

[codecov]

Codecov Report

Merging #2218 (3a7dec8) into main (339896f) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

Impacted Files	Coverage Δ
...rc/awkward/operations/ak_merge_union_of_records.py	88.70% <ø> (ø)

[jpivarski]

I'll take your word for it!

(Sounds like a terrible review, doesn't it? But in this PR, it's clear that you just needed to move tests-cuda-kernels from one category to another for some technical reason in hatchling. The evidence that it was the right thing to do is that it got those header files into the package, and not doing this didn't. Current tests wouldn't have been sensitive to that change, since we're not routinely testing CUDA kernels yet.)

[jpivarski]

src is not in the root of the filesystem, but I suppose this filename path is interpreted by hatchling to be relative to the base of the package or source repo.

[agoose77]

Yep, Hatchling uses Git-style glob pattern to match these entries. This doesn't "fix" any bugs, but it's good to be explicit that we're talking about one src directory only :)

[agoose77]

Sounds like a terrible review, doesn't it?

Haha, sometimes less is more!