Migration client-python source code inside OpenCTI repository #12446
Description
Problem
It is increasingly difficult to maintain our CI/CD, and as we aim to make improvements and move more and more to github actions, we need to rationalize our effort.
Proposed Solution
Migrate https://github.com/OpenCTI-Platform/client-python inside https://github.com/OpenCTI-Platform/opencti/
- keep git history
- migrate issues
- communicate into pending PRs
- prepare new CI and CD
- archive client-python repository
Note that the client-python library follows strictly the same release timeline as opencti (being a binding of the graphql API exposed by octi), which is also in favor of this solution.