feat: add patch version handling in policy conditions and update tran…

[arjavdongaonkar]

…slations

Description

Added a Patched Version Policy that checks if vulnerabilities in a component have a patched version available, and compares this against policy conditions.
This allows policies to trigger when:

• A patched version is present (or)
• A patched version is not present
  based on the configured condition (IS or IS_NOT) and expected value (true / false).

Addressed Issue

Enables policy checks for vulnerabilities based on the presence or absence of patched versions.

Additional Details

• The evaluator looks at all vulnerabilities for a component.
• It treats any non-empty patchedVersions field as "patched version available".
• Invalid policy values for this subject (not true or false) are ignored with a warning in logs.
• Adds flexibility to enforce upgrade-related security policies.

• I have read and understand the contributing guidelines
• This PR introduces new or alters existing behavior, and I have updated the documentation accordingly

[owasp-dt-bot]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)