ci: temporarily disable gitleaks scanning in status-checks

[miguemagicdev]

Description

This PR removes the gitleaks scanning step from the security-audit job within .github/workflows/status-checks.yml.

Context

Currently, the gitleaks step is failing across all PRs due to an invalid/missing license key. Because this step is a required part of our status-checks workflow, it is blocking all merges across the repository.

Why this is happening

• License Issues: The organization is currently experiencing administrative hurdles in procuring/renewing the Gitleaks license.
• Workflow Blockage: Until the license is active, the tool returns a non-zero exit code, invalidating the entire status check suite regardless of code quality.

Security Impact & Mitigation

[!WARNING]
Removing secret scanning increases the risk of accidental credential leakage.

To mitigate this risk while the automated check is offline:

• Manual Review: Reviewers are asked to be extra vigilant regarding hardcoded keys or secrets during PR audits.
• Local Scanning: Developers are encouraged to run local secret detection tools (like detect-secrets) before pushing.

Next Steps

This is a temporary measure. We will revert this change as soon as the organization license is secured and the secret is updated in the GitHub Actions environment.