Features/cli api key creation

[KarixD2137]

I added CLI arguments for API key creation:
--create-api-key <- Creates a new API Key by sending a request to Corebrain-API
--key-name <- Sets name of the new API Key
--key-level read | write | admin <- Sets Access level for the new API Key

Usage example:
corebrain --create-api-key --key-name "Name of the key" --key-level write

I have tested the API Key creation with Corebrain-API. After logging in to SSO and authentication, API keys can be created with CLI command properly.

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
17449842	Triggered	Generic High Entropy Secret	3fac1ed	examples/complex.py	View secret
17449344	Triggered	Generic High Entropy Secret	316f9ec	corebrain/examples/complex.py	View secret
17330250	Triggered	Generic High Entropy Secret	791676b	corebrain/cli/common.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[ceoweggo]

Readme file get conflicts. Fixed in the next commit