feat: add sumologic provider

[35C4n0r]

Closes #1906
/claim #1906

📑 Description

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

ℹ Additional Information

[vercel]

@35C4n0r is attempting to deploy a commit to the KeepHQ Team on Vercel.

A member of the Team first needs to authorize it.

[gitguardian]

⚠️ GitGuardian has uncovered 2 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
-	-	Sumo Logic Keys	28b10a5	keep/providers/sumologic_provider/sumologic_provider.py	View secret
-	-	Sumo Logic Keys	cfd7ee6	keep/providers/sumologic_provider/sumologic_provider.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.}

[talboren]

few small comments + ask for screenshot

[35C4n0r]

@talboren

[35C4n0r]

@talboren thanks for the review, I've made the required changes :)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.75%. Comparing base (6d5c759) to head (d2c9fcc).
Report is 97 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #1924       +/-   ##
===========================================
+ Coverage   30.68%   69.75%   +39.07%     
===========================================
  Files          54      143       +89     
  Lines        5028    11696     +6668     
===========================================
+ Hits         1543     8159     +6616     
- Misses       3485     3537       +52     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
keep	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 15, 2024 2:34pm

[talboren]

lgtm