fix(query): fp for operation without successful http status code when valid codes are present

[cx-artur-ribeiro]

Closes #7600

Reason for Proposed Changes

• The query Operation Without Successful HTTP Status Code was reporting a false positive when a 204 response was defined;
• This was due to the use of the content_allowed helper function, which excluded 204 unless the method was HEAD, even though the query explicitly allows 204 via regex;

Proposed Changes

• Removed the use of content_allowed from the query to avoid unintentionally filtering out valid success codes;
• Updated the query logic to directly check for status codes 200, 201, 202, and 204, while still excluding HEAD operations and status 304 inline;

I submit this contribution under the Apache-2.0 license.

[github-actions]

KICS version: v2.1.13

Category Results CRITICAL 0 HIGH 0 MEDIUM 0 LOW 0 INFO 0 TRACE 0 TOTAL 0	Metric Values Files scanned 1 Files parsed 1 Files failed to scan 0 Total executed queries 47 Queries failed to execute 0 Execution time 0

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
20838717	Triggered	Generic Password	d34ebef	assets/queries/azureResourceManager/sql_server_database_with_alerts_disabled/test/negative8.json	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 secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
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.}