fix(api): update unique constraint for Provider model to exclude soft…

[rakan-pro]

Context

This change addresses an issue where attempting to soft-delete a provider that was already soft-deleted would result in a duplicate error.

Description

This change modifies the unique constraint on the Provider model to ensure that it only considers non-deleted entries.
A new migration has been created to reflect this change in the database schema.
Additionally, tests have been added to verify the behavior of soft deletion and the uniqueness of provider entries.

Steps to review

1. Manual Verification (if possible): If there's an easy way to spin up the API locally, consider:
   • Creating a provider.
   • Soft-deleting that provider.
   • Attempting to create a new provider with the same unique identifier (tenant_id, provider, uid). This should succeed.
   • Attempting to create a new provider with the same unique identifier when the original is NOT soft-deleted. This should fail.
   • Soft-deleting that provider. should not fail (it was failing before due to the UniqueConstraint)

Checklist

• Are there new checks included in this PR? Yes / No
  • If so, do we need to update permissions for the provider? Please review this carefully.
• Review if the code is being covered by tests.
• Review if code is being documented following this specification https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
• Review if backport is needed.
• Review if is needed to change the Readme.md
• Ensure new entries are added to CHANGELOG.md, if applicable.

API

• Verify if API specs need to be regenerated.
• Check if version updates are required (e.g., specs, Poetry, etc.).
• Ensure new entries are added to CHANGELOG.md, if applicable.

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.

[github-actions]

✅ All necessary CHANGELOG.md files have been updated.

[github-actions]

🔒 Container Security Scan

Image: prowler-api:534d3ef
Last scan: 2025-11-07 12:15:34 UTC

📊 Vulnerability Summary

Severity	Count
🔴 Critical	5
Total	5

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

[josema-xyz]

LGTM! 🚀

[josema-xyz]

Love the tests!

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.26%. Comparing base (13e4866) to head (0a559cb).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master    #9054       +/-   ##
===========================================
+ Coverage   54.42%   94.26%   +39.84%     
===========================================
  Files          87      149       +62     
  Lines        2850    18695    +15845     
===========================================
+ Hits         1551    17623    +16072     
+ Misses       1299     1072      -227     

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

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

Components	Coverage Δ
prowler	∅ <ø> (∅)
api	94.26% <100.00%> (∅)

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

[prowler-bot]

💚 All backports created successfully

Status	Branch	Result
✅	v5.13

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details