577 add comprehensive instructions for khiops python development

[popescu-v]

closes #577

---

TODO Before Asking for a Review

• Rebase your branch to the latest version of main (or main-v10)
• Make sure all CI workflows are green This is moot for this kind of updates
• When adding a public feature/fix: Update the Unreleased section of CHANGELOG.md (no date) This is irrelevant to dev chores
• 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

[tramora]

For an human-being like me it seems very clear and comprehensive.

From the root copilot-instructions.md it is easy to follow and apply the corresponding sub instructions.

I'm wondering if it is required to give the workflow counts (7) and the current components versions that will require instructions changes later whenever they change

[popescu-v]

I'm wondering if it is required to give the workflow counts (7) and the current components versions that will require instructions changes later whenever they change

Right, we could abstract these away.

[popescu-v]

I'm wondering if it is required to give the workflow counts (7) and the current components versions that will require instructions changes later whenever they change

Right, we could abstract these away.

On second thought:

• the component versions are just examples (stated as such)
• the release.ymlworkflow has been opportunistically dropped: never used, not up-to-date.

[tramora]

The current status of the instructions is fine for me. There is a fear though about a little repetition regarding the Python code formatting and dependencies within the Python code but it is not blocking.
All these instructions will have to be refreshed soon for the very next Pull Requests

[tramora]

I was surprised that the github workflows run after the instructions update. It was not the case the first time.

[popescu-v]

I was surprised that the github workflows run after the instructions update. It was not the case the first time.

It's because of the first commit which removes an unnecessary file in the tests/ directory.

[tramora]

Looks Good