TA-3749: Define Content CLI foundation

[Zgjim Haziri (ZgjimHaziri)]

Description

We're starting a refactoring on Content CLI with the (main) purpose of defining clear ownership and separating the functionality provided by the tool from the command-specific logic. More details can be found in the linked design doc.

• Defined Content CLI foundation in the top level of this new branch.
• The commands have still not been migrated in the new directory.
• The profile command was migrated in order to test the tool and since it can be considered as part of the foundation.
• Merged two client services into one. Will migrate its usages when migrating the commands.

Notes

• Refactoring was based on the experimenting done on this branch.
• The changes were all done in a base branch content-cli-v2-refactoring which provides a clean state of the repository files besides the nodeJs related files. All the subsequent changes will be merged here, until the refactoring is finished.
• We will check if we can persist history when merging the main content-cli-v2-refactor file, since doing that in this PR on top of a "main-like" branch, seemed to bring too many deletions, especially because we still haven't migrated much of the commands code.

Checklist

• I have self-reviewed this PR
• I have tested the change and proved that it works in different scenarios
• I have updated docs if needed

Relevant links

Jira issue: https://celonis.atlassian.net/browse/TA-3749
Design doc