Validation of `UINT64` values that are out of the range of `number` about 3d-tiles-validator HOT 1 OPEN

As an addendum, related to #260 :

(EDIT: What originally was written here did not make sense, because it referred to a case that was disallowed by the specification. But the core of the question remains, and has been updated accordingly)

When metadata values have the type (U)INT64, it is not always clear in which "space" certain operations should take place. For the validator in particular, this refers to the validation of minimum/maximum values that are described in https://github.com/CesiumGS/3d-tiles/tree/draft-1.1/specification/Metadata#minimum-and-maximum-values :

• When these minimum/maximum values are supposed to be computed from the property table, one would expect them to be computed with bigint for the (U)INT64 types
• They expected minimum/maximum values are defined in JSON, meaning that they are limited to number

Comparing bigint values to number does not make sense in many cases.

from 3d-tiles-validator.