[python] Relax pin: tiledbsoma~=1.11.4

[ryan-williams]

While developing, local tiledbsoma installs get version numbers like 1.11.4.post0.dev3991933300. The tiledbsoma==1.11.4 pin in this repo errors when attempting to install alongside such a tiledbsoma, e.g. in arrayloader-benchmarks:

pip install -e cellxgene-census/api/python/cellxgene_census -e tiledb-soma/apis/python
# ERROR: Cannot install cellxgene-census==1.14.2.dev3+g5de4536.d20240606 and tiledbsoma 1.11.4.post0.dev3991933300 (from $PWD/tiledb-soma/apis/python) because these package versions have conflicting dependencies.
# 
# The conflict is caused by:
#     The user requested tiledbsoma 1.11.4.post0.dev3991933300 (from $PWD/tiledb-soma/apis/python)
#     cellxgene-census 1.14.2.dev3+g5de4536.d20240606 depends on tiledbsoma==1.11.4
# 
# To fix this you could try to:
# 1. loosen the range of package versions you've specified
# 2. remove package versions to allow pip attempt to solve the dependency conflict

tiledbsoma~=1.11.4 (equivalent to tiledbsoma>=1.11.4,<1.12.0) lets such local installs work, and doesn't have any downsides, afaict.

(factored out of #1169)

[ebezzi]

Apologies, the == was introduced by mistake in the last release. Thanks Ryan!

[ryan-williams]

Ah gtk, I hadn't noticed that (dfb2042).

The Docker build GHA here failed with:

ERROR: invalid tag "/cellxgene-census-builder:823a27f": invalid reference format

after checking out SHA 823a27f ("Merge 5de4536 into 5fc72e2").

I'm guessing the issue is that I opened this PR from a branch in my fork. lmk if you want me to open a new one from a branch in this repo, or take some other action?

[ebezzi]

Ah gtk, I hadn't noticed that (dfb2042).

The Docker build GHA here failed with:

ERROR: invalid tag "/cellxgene-census-builder:823a27f": invalid reference format

after checking out SHA 823a27f ("Merge 5de4536 into 5fc72e2").

I'm guessing the issue is that I opened this PR from a branch in my fork. lmk if you want me to open a new one from a branch in this repo, or take some other action?

Yeah, that's a known issue. I will go ahead and merge this. Thanks again!