Add support for UINT32, UINT64, INT64 property table properties

[lilleyse]

We didn't add support for UINT32, UINT64, and INT64 properties in #573 due to several limitations:

• MDL doesn't have uint, uint64, or int64 types, just an int type
• MDL doesn't support reading from integer textures
• MDL and DynamicTextureProvider don't support 64-bit texture formats

It would still be valuable to access these properties in MDL, though. One solution is to encode them in a 32-bit float texture and warn the user about potential precision loss, similar to what's done for FLOAT64.

The main changes would include:

• Allow UINT32, UINT64, and INT64 in MetadataUtil but log warning about precision loss
• Updates in FabricMaterial for handling type conversions of noData, defaultValue, and maximumValue
• Potential changes in MetadataUtil::encodePropertyTables and DataType / DataTypeUtil
• Potential changes in cesium.mdl

The most difficult part will be handling noData, defaultValue, and maximumValue. These may need to be casted to float to match the texture encoding. Is it possible to do this and still use the existing MDL functions cesium_internal_property_table_int_lookup and cesium_internal_property_texture_normalized_int_lookup?

For testing:

• Sample tilesets: 3d-tiles-samples-property-table-types 2024-01-09.zip
• Disable georeferencing on the /Cesium prim since this tileset isn't georeferenced
• Check out the material graph tutorial: https://cesium.com/learn/omniverse/omniverse-style-by-properties/

A few issues might come up as annoyances during development:

• Race condition when loading local tileset with custom materials #542
• Update tiles automatically when material changes #504