Improve messages and behaviour when detecting unhappy installation paths

[tramora]

• in case of major version mismatch, raise immediately an error
• in case of a mix between conda and something else (pip or a cloned source folder), we suggest deactivating the conda env or install the library inside this later
• discourage using system-wide khiops binary and a library inside a conda env

Fixes #515

---

TODO Before Asking for a Review

• Rebase your branch to the latest version of dev (or main for release PRs)
• Make sure all CI workflows are green
• When adding a public feature/fix: Update the Unreleased section of CHANGELOG.md (no date)
• Self-Review: Review "Files Changed" tab and fix any problems you find
• API Docs (only if there are changes in docstrings, rst files or samples):
  • Check the docs build without warning: see the log of the API Docs workflow
  • Check that your changes render well in HTML: download the API Docs artifact and open index.html
  • If there are any problems it is faster to iterate by building locally the API Docs

[popescu-v]

See the comment.
I also think that we should add a test that an exception is raised if the major versions are different between Core and the Python library, in test_khiops_integrations.py plus changes in the CI. Since this test is out of the scope of this PR, I would update issue #382 accordingly with a comment.

[tramora]

The users may be surprised that the major version mismatch raises an exception and cuts the running flow immediately.
I could be changed to delay this and show then a "clean" installation status report.
The major drawback of this alternative is that the users may never run the installation status check and run tasks against an incompatible version of Khiops. The implementation of this PR seems then the best way to raise this error. It the users complain we could think about.

[tramora]

See the comment. I also think that we should add a test that an exception is raised if the major versions are different between Core and the Python library, in test_khiops_integrations.py plus changes in the CI. Since this test is out of the scope of this PR, I would update issue #382 accordingly with a comment.

In my opinion this very border-case of incompatible major version is not worth being implemented into test_khiops_integrations.py and if so it would technically more difficult to reach the dedicated conda environment I'm thinking putting a Khiops10 installation.

It seems simplier to me to stick to the setup into the docker dev images and test directly within the CI workflow (before running test_khiops_integrations.py)

[popescu-v]

The users may be surprised that the major version mismatch raises an exception and cuts the running flow immediately. I could be changed to delay this and show then a "clean" installation status report. The major drawback of this alternative is that the users may never run the installation status check and run tasks against an incompatible version of Khiops. The implementation of this PR seems then the best way to raise this error. It the users complain we could think about.

I think failing immediately if the major versions do not match is the correct behavior, because we are sure, by the convention of the major releases, that the binaries are incompatible with the Python library, hence it seems pointless to execute anything else beyond this check if the major versions do not match.

[popescu-v]

See the comments.

[popescu-v]

Just a few comments left.

[popescu-v]

LGTM