Prepare release 11 0 0 2

[tramora]

Checklist:

• Create branch
• Update CHANGELOG.md
• Update CI workflows [.github/workflows/pip.yml], [.github/workflows/conda.yml], [.github/workflows/dev-docker.yml] and [.github/workflows/tests.yml] to the 11.0.0[-rc.X] Khiops Core and Desktop versions as applicable
• Push this issue branch
• [x] Manually launch the [.github/workflows/dev-docker.yml] workflow on this branch and using the 11.0.0[-rc.X] Khiops core version; select "Push to GH registry"; use tag 11.0.0-rc.X.0 for the Docker image (the last ".0" is the image increment).
• [x] Update default Docker image tag to 11.0.0-rc.X.0 in the CI workflows [.github/workflows/pip.yml], [.github/workflows/tests.yml] and [.github/workflows/api-docs.yml]
• Update __version__ in khiops/__init__.py and version in packaging/conda/meta.yaml to 11.0.0.2
• [x] Update khiops-core package version pin in [packaging/conda/meta.yaml] to ==11.0.0[-rc.X]
• [x] Update the khiops-python-tutorial GitHub repository to the appropriate Khiops Python and Docker image tags: 11.0.0.2-rc.X and 11.0.0-rc.2.0 respectively
• Create PR for this branch, wait for the CI of the PR to be green, then merge the PR into dev
• Git tag dev with 11.0.0.2-rc.X (to match the RC increment of Khiops core)
• Push the 11.0.0.2-rc.X tag on dev; thus, [.github/workflows/pip.yml], [.github/workflows/conda.yml] and [.github/workflows/api-docs.yml] are automatically launched on the 11.0.0.2-rc.X tag; whence, a GitHub pre-release is created, the Pip packages and the documentation archive are pushed to the pre-release, and the Conda packages are pushed to the default khiops-dev channel;
• Manually launch the full automatic tests on the CI (by checking the "Expensive tests" box) on the 11.0.0.2-rc.X tag
• Manually inspect the CI logs on the 11.0.0.2-rc.X tag for the following workflows [.github/workflows/pip.yml], [.github/workflows/conda.yml], [.github/workflows/unit-tests.yml] and [.github/workflows/api-docs.yml] to make sure no warning or error is present therein
• If 11.0.0.2-rc.X tests are successful, then manually launch the [.github/workflows/pip.yml] and request to publish the package on the Test PyPI repository ;
• If 11.0.0.2-rc.X tests are successful, then publish the package on conda-forge:
  • Synchronise or create the personal fork of the conda-forge/khiops-feedstock GitHub repository;
  • Create new branch update-version-to-11-0-0-rc-X on the khiops-feedstock personal fork;
  • Update the following fields in this new branch in the khiops-feedstock/recipe/meta.yaml file:
    • version, to 11.0.0.2-rc.x
    • source: sha256, to the value that is displayed in the "SHA256" field of the "File details" in the Test PyPI repository for the 11.0.0.2-rc.X version
    • the run: khiops-core dependency version to 11.0.0-rc.X
  • [x] Update the channel_targets: - conda-forge <label>, to set to rc in the recipes/conda_build_config.yaml file
  • Create new pull request on the newly-created Git branch in the khiops-feedstock repository
  • Ask to re-render the repository according to the PR (follow the instructions on the PR).
• ~~[x] Once khiops-core gets updated to the final 11.0.0 release, re-do all previous steps, with the following changes:
  - Khiops Core and Desktop package versions changed to 11.0.0 in [.github/workflows/pip.yml], [.github/workflows/tests.yml] and [.github/workflows/api-docs.yml];
  - Khiops Core dependency changed in [.github/workflows/conda.yml] and in the khiops-feedstock/recipe/meta.yaml file.
• [ x] Create (and merge) PR to update back default Docker image tag to 'latest' in the CI workflows [.github/workflows/pip.yml], [.github/workflows/tests.yml] and [.github/workflows/api-docs.yml] on dev.
• If tests are successful, then create Git tag 11.0.0.2 on the dev branch.
• Launch the [.github/workflows/conda.yml] and [.github/workflows/pip.yml] workflows on the 11.0.0.2 tag to publish the 11.0.0.2 on the khiops-dev Conda channel and on the GitHub release space and on the Test PyPI repository.
• If the previous step went well, launch [.github/workflows/pip.yml] manually, on the 11.0.0.2 tag, while selecting PyPI as target repository.
• Publish the 11.0.0.2 Python package on the conda-forge/khiops-feedstock repository, on the main label.
• Copy relevant CHANGELOG.md contents to the 11.0.0.2 GitHub pre-release;
• (After the Conda package has been published on the conda-forge channel) Transform the 11.0.0.2 GitHub pre-release into a release.