fix: make CodeVulnerability and UngroundedAttributes scoring patterns binary

[slister1001]

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new API spec, a link to the pull request containing these API spec changes should be included above.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[Copilot]

Pull request overview

This PR fixes a bug where the code_vulnerability and ungrounded_attributes evaluators were missing from the EVALUATOR_SCORING_PATTERNS registry. These evaluators return boolean labels (True/False) and should use the BINARY_TRUE_FALSE scoring pattern, consistent with similar evaluators like sensitive_data_leakage, protected_material, and task_adherence.

Key Changes:

• Added code_vulnerability entry to EVALUATOR_SCORING_PATTERNS with BINARY_TRUE_FALSE pattern
• Added ungrounded_attributes entry to EVALUATOR_SCORING_PATTERNS with BINARY_TRUE_FALSE pattern