Using min in a precision range results in an InvalidSchemaException

[popematt]

E.g.:

$ion_schema_2_0
type::{
  name: foo,
  precision: range::[min, 5]
}

Results in:

Precision must be at least 1 (range::[min,4])
com.amazon.ionschema.InvalidSchemaException: Precision must be at least 1 (range::[min,4])
	at com.amazon.ionschema.internal.constraint.Precision.<init>(Precision.kt:33)
        ...

The spec says that any positive int range is okay for precision, so the precision constraint should be interpreting min as 1 rather than 0.

This issue affects all versions of ISL.