Add Constraints on Conda Driver Packages Versions

[popescu-v]

Description

Conda driver package versions are constrained with respect to the khiops-core versions. These can (and should) be enforced in the Conda packaging script.

Questions/Ideas

• Update run_constrained in packaging/conda/meta.yaml by adding the required version borders for the Conda packages of the S3 and GCS drivers.

[popescu-v]

Decisions:

• add both S3 and GCS drivers as strong runtime dependencies to the khiops-core Conda package.
• bump the khiops-core Conda package build number when updating the driver packages' versions; thus, the khiops-core version stays the same and reflects, as of now, the evolutions of khiops-core itself. ~However, we need to check if / how the users' environments get updated when the build number is bumped, but the version is kept.~ (see next comment)

[bruno-at-orange]

This doc, tells us that

Conda uses build_bumber to sort packages that have otherwise identical names and versions to determine the latest one.

Then I think it is not necessary to check if the package is updated in the user's environment when the build_number is incremented.en i think it is not necessary to check if the package is updated in the user environment when the build_number is incremented.

[popescu-v]

Cannot be done unless the driver packages are published on conda-forge first.

[popescu-v]

Superseded by https://github.com/KhiopsML/khiops/issues/597.