chore(release): Bump version to v5.22.0

[prowler-bot]

Description

Bump Prowler version to v5.22.0 after releasing v5.21.0.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

✅ Conflict Markers Resolved

All conflict markers have been successfully resolved in this pull request.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.53%. Comparing base (0f2fdcf) to head (d119472).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #10389       +/-   ##
===========================================
+ Coverage   56.86%   77.53%   +20.66%     
===========================================
  Files          87        1       -86     
  Lines        2847      138     -2709     
===========================================
- Hits         1619      107     -1512     
+ Misses       1228       31     -1197     

Flag	Coverage Δ
prowler-py3.10-config	77.53% <100.00%> (?)
prowler-py3.10-oraclecloud	?
prowler-py3.11-config	77.53% <100.00%> (?)
prowler-py3.11-oraclecloud	?
prowler-py3.12-config	77.53% <100.00%> (?)
prowler-py3.12-oraclecloud	?
prowler-py3.9-config	77.53% <100.00%> (?)
prowler-py3.9-oraclecloud	?

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
prowler	77.53% <100.00%> (+20.66%)	⬆️
api	∅ <ø> (∅)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

🔒 Container Security Scan

Image: prowler:dc87087
Last scan: 2026-03-19 12:11:00 UTC

📊 Vulnerability Summary

Severity	Count
🔴 Critical	4
Total	4

4 package(s) affected

⚠️ Action Required

Critical severity vulnerabilities detected. These should be addressed before merging:

• Review the detailed scan results
• Update affected packages to patched versions
• Consider using a different base image if updates are unavailable

---

📋 Resources:

• Download full report (see artifacts)
• View in Security tab
• Scanned with Trivy