remove nested types in CLValue

The current implementation of CLValue contains nested CLTypes (map, result, tuples) that make it overly complicated to serialize and deserialize. This is because each of the nested types must be serialized individually before the overall Value can be serialized. The objective of this ticket is to remove the nesting of these types in order to streamline implementations of the clients.