feat(queries): fix custom has key construct regal lint issue

[cx-artur-ribeiro]

Fix custom has key construct regal lint issue

This PR replaces custom key existence checks using the has_key function with the more efficient and idiomatic in operator and object.keys method. This change improves code readability, performance, and aligns with Rego best practices by eliminating the need for custom functions in favor of built-in constructs.

Reason for Proposed Changes

• Ensure compliance with Regal Linter’s custom-has-key-construct rule;
• Improve performance and readability by replacing custom functions with standard Rego constructs;
• Align with Rego best practices and enhance maintainability by using idiomatic patterns for key existence checks.

Proposed Changes

• Replace has_key(x, k) or exists(x,k) with k in object.keys(x) where appropriate;
• Ensure all affected files pass Regal Linter without custom-has-key-construct warnings.

Continuation of #7295

I submit this contribution under the Apache-2.0 license.

[github-actions]

KICS version: v2.1.4

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