Wrong type check for `min/max` in class properties

[javagl]

^{(EDITED - The description here was originally the "opposite" of the actual issue...)}

When a VECn class property defines min/max values, then this can lead to a wrong ARRAY_ELEMENT_TYPE_MISMATCH issue.

For example, the following:

{
  "id": "EXAMPLE_ID",
  "classes": {
    "exampleClass": {
      "properties": {
        "exampleProperty": {
          "type": "VEC2",
          "componentType": "FLOAT32",
          "min": [1.0,1.0]
        }
      }
    }
  }
}

will cause an ARRAY_ELEMENT_TYPE_MISMATCH for the min value.

The fix is trivial, and already underway.