Allow schemas to use unevaluatedProperties: false instead of additionalProperties: false

[DavidBiesack]

JSON Schema 2020-12 (used in OAS 3.1) defines a new keyword, unevaluatedProperties which is like additionalProperties but works better when using JSON Schema composition with allOf.

For this feature, extend the OWASP ruleset to check if unevaluatedProperties is used and enforce the value false for it.
and also the rule that allows a non-false value for unevaluatedProperties only if maxProperties is also set.

Context

Avoid a false negative when a schema uses unevaluatedProperties: true

Current Behavior

Unlike additionalProperties: true or additionalProperties: { .... },
any use of unevaluatedProperties: true or unevaluatedProperties: { ... } in a schema is not flagged.

Expected Behavior

issue a warning when unevaluatedProperties: true or unevaluatedProperties: { ... } is used in a schema

Possible Solution(s)

Clone the owasp:api6:2019-no-additionalProperties and owasp:api6:2019-constrained-additionalProperties in ruleset.ts and modify to address unevaluatedProperties instead. New rules:
owasp:api6:2019-no-unevaluatedProperties owasp:api6:2019-constrained-unevaluatedProperties