Prepare the 11.0.0.3 Release

[popescu-v]

• Create dedicated Git branch
• Launch expensive tests manually on this branch
• Update the CHANGELOG.md file with the proper version and release date on this branch
• Create PR on this branch
• Let the Pip package workflow launch automatically on this branch to see there is no error
• Let the Api-docs workflow launch automatically on this branch to see there is no error:
  • Inspect workflow execution log to see there are no build warnings
  • Donwload and inspect the generated docs locally to see there is no apparent issue
• If everything goes well after these stages, ask for review on the PR
• If the review is OK, then merge the PR branch into the main branch
• Tag the main branch with the 11.0.0.3 Git tag
• Let the Pip package publishing workflow launch automatically on the 11.0.0.3 Git tag, to trigger GitHub pre-release creation
• Let the Api-docs workflow launch automatically on the 11.0.0.3 Git tag to trigger API docs tarball dump into the GitHub pre-release.
• After the success of these stages, manually launch the Pip package publishing workflow on the 11.0.0.3 Git tag, to publish the package on Test.PyPI
• Manually install the khiops package from the test.pypi repository into a local virtual environment and perform some tests:
  • That the installation went well, with all dependencies correctly installed in the virtual environment
  • That the import khiops.core as kh; kh.get_runner().print_status() works well inside a Python console launched in the virtual environment
• If all the above tests are successful, then manually launch the Pip package publishing workflow on the 11.0.0.3 Git tag, to publish the package on the PyPI repository
• Publish the release on the conda-forge Conda channel:
  - [ ] Synchronise the personal fork of the khiops-feedstock Git repository in the conda-forge group on GitHub (https://github.com/conda-forge/khiops-feedstock/) with the upstream
  - [ ] On the personal fork of the Khiops feedstock, create branch based on the main branch
  - [ ] On that branch, update the Conda recipe: bump the version and update the SHA256 of the package tarball
  - [ ] Create PR onto the upstream repository on conda-forge
  - [ ] Ask to re-render on that PR
  - [ ] Ask for review of that PR, then, after approval, merge it into upstream
  - [ ] Check that the package is successfully published on conda-forge
• Copy the CHANGELOG.md update regarding the 11.0.0.3 release to the 11.0.0.3 GitHub pre-release description
• Turn the 11.0.0.3 GitHub pre-release into a release and set it as "latest"