update(query): add cwe infos to dockerCompose queries

[ArturRibeiro-CX]

Closes #7006

Reason for Proposed Changes

• dockerCompose queries don't provide cwe infos;

Proposed Changes

• add cwe infos to all dockerCompose queries;
• add cloudProvider common to all queries;
• add oldSeverity to queries metadata;
• update e2e with cloudProvider and cwe field;
• fix typo on query description;
• fix negative2 and positive3 test samples since they were wrongly constructed;

I submit this contribution under the Apache-2.0 license.

[github-actions]

KICS version: v2.1.1

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 48 Queries failed to execute 0 Execution time 0

[cx-ruiaraujo]

LGTM!
For all pipelines to pass, PR-7153 needs to be merged first.

[gitguardian]

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

GitGuardian id	GitGuardian status	Secret	Commit	Filename
4266006	Triggered	Generic Password	ae095d2	assets/queries/common/passwords_and_secrets/test/negative42.yaml	View secret
4266006	Triggered	Generic Password	ae095d2	assets/queries/common/passwords_and_secrets/test/negative32.yaml	View secret
4266030	Triggered	Generic Password	ae095d2	assets/queries/common/passwords_and_secrets/test/positive8.json	View secret
4266030	Triggered	Generic Password	ae095d2	assets/queries/common/passwords_and_secrets/test/positive8.json	View secret
4266030	Triggered	Generic Password	ae095d2	assets/queries/common/passwords_and_secrets/test/positive8.json	View secret
4266030	Triggered	Generic Password	ae095d2	assets/queries/common/passwords_and_secrets/test/positive8.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 secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
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.}

[JulioSCX]

LGTM, great job adding the CWEs to all queries as well as fixing other smaller issues you found along the way!

[EduardoSemanas]

LGTM