Schema defines constraining properties alongside enum

Issue ID: v3-warning-schema-enum-property-improper

Description

A schema in your API definition defines constraining properties alongside enum. While this is allowed, it might not be what you want to do.

Enums themselves are already fully constrained: only exact matches to enum in input or output are accepted. Therefore, adding further constraining properties alongside enum is redundant and can be confusing.