Split tarantoolTuple to tuple with metadata and vise versa

[ArtDu]

it seems we need a new interface class TarantoolTupleWithMetadata extends TarantoolTuple, where we will take out all the methods for working with fields by name. This will be most convenient for the user - he will not see the methods of working with fields from the blunders that have returned from the box API, and in order to use these methods, he will have to explicitly check instanceof and cast to the new interface.

Now, in fact, users should catch an exception that there is no metadata or contact only by field numbers.

The method with checking that the metadata is there will help in springdata, but this problem will remain with users - they will continue to compile code that gives an error in runtime.