If you setvalidation.min orvalidation.max to 0 in a rich parameter, we skip validation.

This makes it impossible to correctly enforce a parameter range where 0 is the min or max, e.g. 0-9.

Spotted during a code read:

Unfortunately this needs to be resolved at the protobuf / data persistence layer, since we only store the min and max, and not whether either or both were explicitly set in the terraform.

cc@mtojek