Produce packages for python 3.12

[dudoslav]

In order to solve environments with python 3.12 we require tiledbsoma-py to support python 3.12 as well.

I removed support for pyarrow 11, not sure if that is an issue.

[johnkerl]

LGTM although I defer to @jdblischak for expert approval on all things Conda

[jdblischak]

You are running into the same problem as I did in #220. Unfortunately conda_build_config.yaml is not flexible enough to accommodate both the outdated py39 cloud variant and a cutting edge py312 build at the same time.

Given that we are going to want to build and test a py312 cloud environment before replacing our existing py39 cloud environment, I don't see any way around having to maintain two separate branches (one for the py39 cloud variant, and one with the latest conda-forge pins).

[jdblischak]

That pyarrow 11 pin is for the cloud variant we install in our py39 environment

# TileDB Cloud genomics notebook image
date
## Mon Nov 18 05:10:35 PM UTC 2024
conda list pyarrow
## # packages in environment at /opt/conda:
## #
## # Name                    Version                   Build  Channel
## pyarrow                   11.0.0          py39hf0ef2fd_5_cpu    conda-forge
## pyarrow-hotfix            0.6                pyhd8ed1ab_0    conda-forge

[jdblischak]

Unfortunately pyarrow 11 is available for py311 but not py312:

mamba create --dry-run -n test -c conda-forge python=3.11 pyarrow=11
##   + pyarrow                   11.0.0  py311hdf9aeb4_60_cpu  conda-forge        4MB

mamba create --dry-run -n test -c conda-forge python=3.12 pyarrow=11
## Could not solve for environment specs

[jdblischak]

Went with the 2-branch approach. Superseded by #227 and #228