feat!: make schema_version 64-bit

This feature was inspired by the problems in sbroad. Some of our customers use vinyl spaces in the SQL queries. As far as Tarantool doesn't support cross-engine queries we are not able to create virtual tables for the queries with vinyl spaces other than vinyl (no memtx's meta-temporary can help us in this case). So, we have to create and drop lot's of virtual tables made from vinyl spaces and increment the 32-bit schema version. Easy to guess that such solution can't be used in production. As far as we don't want to cancel the vinyl engine support I suggest to increment the counter to 64 bits. Even if the user produces 10^6 schema version bumps per second, we still have 578 * 10^9 years to solve this issue.

BREAKING CHANGE: previously the schema version was a 32-bit unsigned. But it can become a problem for applications that widely create vinyl spaces. As far as vinyl can't be set meta-temporary, its creation always increments the schema. Let's make this counter 64-bit unsigned to avoid the overflow problem. As a side effect be break the IPROTO compatibility with the previous versions of Tarantool.