[TODO] Wheel exposure #2
Description
It's often the case that wheels are put into the same GHA artifact as an sdist. We need a way to expose them to the caller, who can then use them for testing.
I was thinking of an output that points to such a wheel, which is okay when there's just one (e.g. for pure-python projects or "cext" projects with a pure-python fallback wheel). For projects with many wheels, that wouldn't work, since the usable (compatible) wheel would differ depending on the runtime. So, maybe it makes sense to just expose the directory, right?
Another idea is wrapping the previous yarl experience of determining compatible wheels into a dedicated action: https://github.com/aio-libs/yarl/blob/8d28329/.github/workflows/ci-cd.yml#L165-L202.