feat: multiple alerts matching rules PoC

[VladimirFilonov]

Closes #2776

📑 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]

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

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
keep	⬜️ Ignored (Inspect)	Visit Preview		Dec 25, 2024 8:18am

[codecov]

Codecov Report

Attention: Patch coverage is 24.57627% with 89 lines in your changes missing coverage. Please review.

Project coverage is 30.99%. Comparing base (6adf5bc) to head (44ce577).
Report is 12 commits behind head on main.

Files with missing lines	Patch %	Lines
keep/rulesengine/rulesengine.py	21.79%	61 Missing ⚠️
keep/api/core/db.py	17.39%	19 Missing ⚠️
keep/api/bl/incidents_bl.py	20.00%	8 Missing ⚠️
keep/api/models/db/alert.py	66.66%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #2727       +/-   ##
===========================================
- Coverage   43.63%   30.99%   -12.65%     
===========================================
  Files         162       71       -91     
  Lines       15789     7957     -7832     
===========================================
- Hits         6890     2466     -4424     
+ Misses       8899     5491     -3408     

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

[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.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
8134198	Triggered	Generic High Entropy Secret	c8b293a	keep-ui/app/frigade-provider.tsx	View secret
14884154	Triggered	Username Password	3046854	elk/docker-compose-elk.yml	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.}

[Kiryous]

LGTM!