Investigate tuples with same field names but different order

[baseTwo]

Currently the new value tuples contain the first parameter with CqlTupleMetadata which contains the tuple item types and names. Equality of tuples are equal for tuples with exactly the same CqlTupleMetadata and the remaining values in the tuples.

But should we consider that the order of fields names should not matter? After all, it should be considered as a dictionary. So (a:1, b:"b") should be equal to (b:"b", a:1)

This needs to be investigated

[EvanMachusak]

The order of tuple elements does not matter. I had to fix a similar bug in HEDIS in which we had functions like this:

define function Foo(t Tuple{ x: Integer, y: String })
define function Foo(t Tuple{ y: String, x: Integer })

Those are the same function and an ambiguity error must be raised.

My solution to this was always to sort the tuple's elements alpha ascending before creating it as a type.