Check value is array before passing to DataValueDeserializer::newFromArray

[filbertkm]

It's possible that a value being handled in DataValueDeserializer::newFromArray is not an array, so we need to check.

Bug: T168681

[filbertkm]

my guess is that the issue is a bot is misbehaving and passing bad input.

todo: add tests to cover this

[manicki]

I guess this might work, and I am happy to write tests etc if this is the way we want to go.

That said, looking at other data values classes than UnboundedQuantityValue which was related to the issue referred to above, it seems other classes provide less strict newFromArray, allowing all input and throwing an exception if the value is not an array (i.e. not the language-level error).
I am wondering whether we wouldn't like to to adjust UnboundedQuantityValue::newFromArray the same way. I filed wmde/Number#105 in case this was preferred.

DataValueDeserializer already handles the exception UnboundedQuantityValue::newFromArray would throw, so this should also solve the issue I believe.

[thiemowmde]

Oh dear. This is not the correct fix. Look at StringValue, for example. It expects a string, not an array. We need to do bugfix releases of the geo and number components instead. I will explain in more detail in the Phabricator ticket.