Patch aa549401 "Split key_def.h/.cc" accidentally added
FIELD_TYPE_MAP member to `enum field_type`. Currently this
enum is only used to define index parts. We don't support
'map' indexed field type at least in 1.7.x.

See #2652

Part of #2652

In the next patches the field_def will being parsed from space:format.
Field_def will contain char *name, which is limited by BOX_NAME_MAX = 65000.
So neither opt_type OPT_STR or OPT_STRPTR can be used to parse this name from
space:format. Besides, field_def contains enum field_type, which can not
be parsed using and opt_type.
Also, field_def will contain default_value, which can store values of
many types.

Proposal is to use opt_create_from_field not for entire field_def, but only
for several fields using opts_parse_key. And parse other options
manualy.

Needed for #2652

replication/cluster.test.py would fail at server exit, because
at_exit() handler tries to destroy a cbus while its mutex is locked.

args.test.py would fail when run with 'make test'

fiber_time() reports real time, which shouldn't be used for calculating
timeouts as it is affected by system time changes. Add fiber_clock()
based on ev_monotonic_now(), export it to Lua, and use it instead.

Needed for #2527

We should use ev_monotonic_now()/ev_monotonic_time() instead of
ev_now()/ev_time() for calculating timeouts, because the latter
are affected by system time changes so that using them for timeouts
can lead to unexpected hangs in case system time changes.

Needed for #2527

ev_now()/ev_time() are affected by system time changes, which makes them
impractical for calculating timeouts. Introduce ev_monotonic_now() and
ev_monotonic_time() which work exactly as ev_now()/ev_time(), but use
monotonic clock instead of realtime.

Needed for #2527

Follow up #1265

Follow up #2662

Finally fix compatibility with Lua 5.1 command-line options.

Closes #1265

`tarantool -` now executes stdin instead of trying open "./-" script.

A part of #1265

  -e EXPR - execute string 'EXPR
  -l NAME - require library 'NAME'

A part of #1265

`tarantool -i SCRIPT` forces Tarantool to enter into interactive
mode after executing SCRIPT or stdin.

A part of #1265

getopt_long() is available on all supported platforms.
Get rid of legacy gopt and use getopt_long().

Incompatible changes:

 * `tarantool --version --no-such-option` printed
    "unrecognized option '--no-such-option'", now it displays version.
    `tarantool --no-such-option --version` still prints an error message.

Needed for #1265

- Reference vy_index for every tx value.
- Abort transaction on commit if format was changed by DDL.

Fixes #2342

Check that Tarantool doesn't crash when space remove
while cursor is open.

Fixes #2342

Disconnect replications slave if no ACKs have been received for a
time of `replication_timeout`. This parameter is accessible
via box.cfg{} and applies to all new slave connections.

Follow up #2484

Handle mixed replica_id transaction for wal=none mode.
Follow replicaset vclock after wal writes.
Follow @05eef5fa

On schema version update netbox starts schema reloading but not
disconnects from remote server, so report state as connected for this
case
Fixed #2665

On cpipe_destroy all queued messages were flushed to endpoint but queue
length counter was not zeroed. This breaks an empty pipe check at
cpipe_flush_cb and then crashes tarantool in cases if corresponding endpoint
has been already deleteted before this callback invocation.
Fixed #2703

Replace dynamic function pointers with link-time resolving.

Needed for #2335

Don't resend relay vclock if not changed because a relay loop might be
woken up with cbus messaging.

Now system space formats contain conflicts between space:format,
their index parts and actual tuple fields.

Such formats can not be used to check tuple fields in SQL.

Fix them in order of #2652

strlen() can not be called on message pack auth data. Besides, auth
data can be not only string, but also array or map. And if
array/map is empty, strlen() returns > 0 - it is incorrect.

Needed for #2652

- Use malloc() as a fallback for lsregion for large size
- Set Vinyl slab_size to 16Mb and don't use vinyl_max_tuple_size
  for calculation
- Allow dynamic configuration of vinyl_max_tuple_size

A part of #2342

On 64-bit iconv called via ffi returns a uint64_t cdata object, which
equals to -1 in case of error so error handling works fine. On 32-bit it
returns a number equal to (size_t)-1, which is equal to 4294967295 and
not equal to -1 when compared to in Lua. As a result Lua binding to
iconv hangs if the source string is incorrect. Fix this by comparing the
result of iconv to ffi.cast('size_t', -1) instead of -1.

Closes #2466

Follow up #2334

An on_replace trigger on replica can issue local changes
using its own replica_id. Check replica_id for every row
during writing to WAL.

Fixes #2682

Fix minor issues found by coverity scan:
 - Do not try to estimate slice size if the run is empty to avoid div/0.
 - Fix assert() that is supposed to check slice->first_page_no, but
   checks last_page_no instead.
 - If the slice doesn't intersect with the run (i.e. slice->end is less
   than or equal to run->begin), leave its stats zeroed out.

Closes #2698

The bug happens when some TX deletes a statement (writes it to
its own write set) and then reads a range of tuples containing
that deleted statement. DELETE must not come to select result
(in this and only transaction before it is committed) and
just are skipped by read iterator. After such a skipping and
getting next true (non-DELETE) statement the iterator considers
that there is no data between the previous statement and the
current, and add them to the cache as a chain. This is wrong
because the data could be hidden by DELETE statement.

Track such jumps over TXW DELETE statements in read iterator and
do not add statements as a chain in this case.

We use a binary tree for tracking reads (read_set). The tree is ordered
by (index, statement, tx). Insertion of a partial statement into the
tree may result in breaking comparison transitivity, which is mandated
by the tree implementation. However, for range requests we insert the
search key into the read set, which may be partial. This may result in a
crash in the read_set.

Tracking the search key doesn't make much sense anyway: it doesn't bring
us any closer to range request tracking, only obscures the semantics of
select. So let's track only statements actually returned by the iterator
plus gaps found by point requests.

Closes #2675

Fix bad merge of 945a97db and 7a5835f4