At the moment our grammar doesn't support any sub-queries in the
projection list. So it is a waste of CPU resourcies to transform
projection lists (a big performance penalty for projections with
a huge amount of columns).

Previously for every query we hold a mutable reference on an engine
and tried to load a cluster metadata if the cache was empty. The
problem was that tarantool yields on a first query uploading the
cache to a new one, that also tries to get a mutable reference to
the engine.
The main problem was that we should never hold a mutable reference
to an object with a Lua code, that can be yielded by tarantool
(such behavior is opaque to the Rust compiler). To deal with it we
shrink a metadata upload to a list of separate methods. For the
ones that can yield we always hold an immutable reference. Those
methods that need a mutable reference to the engine never yield.

Basically callbre means that we call replicaset with two additional parameters:
    1) prefer_replica = true. We can use read from replicas because
        transactional consistency is out of Sbroad scope. Basically we
        do not care about data consistency at all.
    2) balance = true. This parameters enables internal vshard load
        balancing between replicaset nodes in round-robin fashion,
        with a preference for replicas if prefer_replica=true is also set

We have fixed some bugs about NULL and made equality propagation
use the infrastructure common with the other transformations.

Also, extended and refactored the tests.

Merge 2 execute query functions in one. Response waiting timeout was extracted to cluster config.

Was made determining uniq set of replicaset by set of buckets that avoid send the same queries to the same replicas. Bucket exec query function was fixed to async mode.

Closes an error in the backend AST reordering logic

Now we can eliminate buckets with multi-column (i.e. composite)
keys in equalities. Previous implementation was incorrect, so
we have to make an executor refactoring as well.

Add support join query to linker, now executor can execute join query with distribution conflict (plan has motion nodes). Extend text in some error