Handle pre-releases for `integration-testing`

[ilan-gold]

Option 1

We should have a pre-release job where we test against pre-releases and anndata's main branch (maybe).

For example, recently, pandas>=3 came out for real, anndata was ready by upper bounding, but on main was ready for the actual package release (i.e., via pre-release jobs).

However, by upper bounding, and not having a pre-release of anndata, we prevented downstream packages from updating their pre-release jobs.

Furthermore, we could override doc could be added as well when we knew something is in preleases

Option 2

Nightly builds (for anndata) that the upstream repos are tested against

[flying-sheep]

To ensure that some newer packages are installed, we have two options I think:

1. uv pip install --overrides=overrides.txt to force e.g. pandas>=3
2. mandate that tested packages don’t have upper bounds on the main branch
   • they either have to use patch branches to make releases with upper bounds or if they only release from the main branch, they have to deal with the integration test job being broken for that time
   • if one of their transitive dependencies upper-bounds something, we have no control

PS: here’s a list of currently unfixed jobs: https://github.com/issues?q=sort%3Aupdated-desc%20is%3Aissue%20is%3Aopen%20archived%3Afalse%20team%3Ascverse%2Fanndata

[grst]

While I think we can recommend (2), I don't think we can enforce it.
So I think (1) is the way to go!