tiledbsoma 1.6.0 pre-release check 1

[johnkerl]

As usual: https://github.com/single-cell-data/TileDB-SOMA/wiki/Branches-and-releases

except: single-cell-data/TileDB-SOMA#1926 (comment)

-- here we need to validate:

• core 2.18
• tiledb-py 0.24
• tiledb-r 0.22
• pyarrow as noted in the linked issue above

There will be a somacore bump later, and another tiledbsoma PR, before 1.6.0 -- so there will be a second Conda pre-release-check PR, following on this one

[jdblischak]

I suspect that the error loading S3 objects described in single-cell-data/TileDB-SOMA#1926 (comment) is a runtime-only error. However, given the complexity of the libarrow run_exports, I agree it is safest to also enforce these pins at build time

[johnkerl]

@jdblischak my thoughts exactly

[johnkerl]

This pre-check PR has green CI, which is its only job:
https://github.com/single-cell-data/TileDB-SOMA/wiki/Branches-and-releases

[jdblischak]

I checked the build logs to confirm that:

1. pyarrow < 13 was installed for the osx and osx-arm64 builds (typically pyarrow 11 or 12 was installed)
2. pyarrow-hotfix was installed for all the builds

Interestingly, for the linux builds (except py37), tiledbsoma-py was built against pyarrow <13, but then pyarrow 14.0.1 was installed at runtime. Thus the libarrow run_exports constraints might not be as strict as we had thought. My guess is that since we depend on pyarrow (and not directly on libarrow), that its max_pin = "x" doesn't apply to tiledbsoma-py (to be clear, I don't think we need to change anything, just documenting the builds)