fix(query): fix false positive in schema_required_property_undefined

[haroldb1]

…when sole required property

The predicate all([property | property != requiredProperty; _ := schema.properties[property]]) was logically inverted, producing two failure modes:

• False positive: when requiredProperty is the only entry in properties, the comprehension yields [] and all([]) is vacuously true — the rule fires even though the property is correctly defined.

• False negative: when requiredProperty is genuinely absent but sibling properties exist, the comprehension yields a non-empty list of strings and all(["sibling"]) is false — the rule does not fire, missing a real violation.

Replace with a direct absence check: not schema.properties[requiredProperty] This evaluates to true if and only if the required property has no entry in properties, regardless of how many siblings exist.

Fixes #8081

Tests:

• negative7.yaml: sole required property present — must not fire (was false positive)
• positive7.yaml: required property absent with sibling present — must fire (was false negative)
• All six existing positive fixtures continue to fire (regression-checked locally)

Closes #

Reason for Proposed Changes

Proposed Changes

I submit this contribution under the Apache-2.0 license.