make sure extra status code entered in related mantis issue are reverted when this is fixed

Because enumerations do not allow every possible Int32 value they received special treatment in many of the scripts by either allowing a BadOutOfRange or excluding them from the script completely. This results in the fact that Enumerations are not being tested to the amount they could be. In order to change that the Increment, SetValueMax, SetValueMin and other help functions need to be enhanced to read the possible values and chose a valid number according to their purpose. Also for those functions the item needs to be passed in instead of only the value.
During the fixes we noticed that there were also other DataTypes missing/wrong and so they did get add and/or updated as well.

In order to use the new functionality added for enumeration the test scripts now need to call the functions providing the complete item not only the value by e.g. calling UaVariant.Increment( { Item: item } );
instead of
UaVariant.Increment( { Value: item.Value } );
for backward compatibility this is still supported but won't benefit from the updates. Other scripts will be updated with the related mantis 5192

review in CMP call