Exception for vector- or matrix typed `noData` metadata values without `default`

(Similar or related to https://github.com/CesiumGS/cesium/issues/11796 )

The [`MetadataTableProperty.get` function](https://github.com/CesiumGS/cesium/blob/737c4538d587767008fcd7a1dfce67213180fb77/packages/engine/Source/Scene/MetadataTableProperty.js#L329) checks wheher the given value is a `noData` value, by passing it to [`MetadataClassProperty.handleNoData`](https://github.com/CesiumGS/cesium/blob/737c4538d587767008fcd7a1dfce67213180fb77/packages/engine/Source/Scene/MetadataClassProperty.js#L826). When the value is a vector type (for example, a `VEC3` that arrives there as a 3-element `number` array), and it is the same as the `noData` value, then the `handleNoData` function will return `undefined`, In this case, the value will be set to the `default` value, and passed to `unpackVectorAndMatrixTypes`. But when the `default` value is _also_ `undefined`, then this will lead to an exception at the end of `unpackVectorAndMatrixTypes`.


Reported at https://community.cesium.com/t/metadata-property-vector3-float32-throws-exception-when-using-nodata/29655 with test data at https://github.com/bertt/cesium_issues/tree/b14b8f8af2aa0c289000b3b095270d0e8e195672/vector3_float32_nodata

Read packages/engine/Source/Scene/MetadataTableProperty.js around MetadataTableProperty.get and packages/engine/Source/Scene/MetadataClassProperty.js around MetadataClassProperty.handleNoData and unpackVectorAndMatrixTypes. Reproduce the vector noData case using the linked test data, then verify that a vector or matrix noData value without a default no longer throws an exception.

Written by the indexing model from the issue text.