Conda release support?

We are running into race conditions when installing duckdb + duckdb-spatial in multi-thread workflow managers like Snakemake.
This happens when executing scripts in parallel that contain `INSTALL spatial; LOAD spatial` in them.
For now only Windows machines seem to be affected.

#### Proposed solution

I believe this could be sidelined by pre-installing these tools on the conda environment.
This works as the environment will be created before the parallel scripts are executed, effectively avoiding the conflict.

Unfortunately, `duckdb-spatial` is not in conda-forge. This is contrary to other duckdb extensions (e.g., https://anaconda.org/channels/conda-forge/packages/duckdb-extension-httpfs/overview).
Could you consider an automated `conda` release as an alternative installation method?

#### Additional context

I am aware of the pip packages (https://github.com/santosh-d3vpl3x/duckdb_extensions).
However, pip tends to conflict with conda dependencies as they silently overwrite conda pins in many cases.