Build a cross Python version conda package

[fabiencelier]

At the moment we release one Conda package per OS and per Python version (while we have one wheel per OS but cross Python versions.)

It would be nice to manage to release only one Conda package per OS so we don't have to do new releases when there are new Python versions.

The difficulties are in conda build. When building the package, the Python files always end up in the folder of a pinned Python version such as "lib/python3.8/site-packages".

Here is a discussion about it.

A possible solution would be to release 2 Conda packages:

• jdk4py-bin which is OS dependent, containing all the java runtime without any Python code.
• jdk4py which is a noarch package importing jdk4py-bin and exposing it as a Python library.

[tibdex]

Just some information for future readers.

The deployment action runs on a single version of Python:

https://github.com/atoti/jdk4py/blob/03107298930649441c042c9d84267ab55b6db78d/.github/workflows/deployment.yaml#L19-L22

but multiple versions of the Conda package are built thanks to this config:

https://github.com/atoti/jdk4py/blob/03107298930649441c042c9d84267ab55b6db78d/conda.recipe/conda_build_config.yaml#L1-L4