Net.box usage for console is deprecated in 1.10,
replaced it with console.

Closes: #3490

Add propagation to luarocks of --only-server, --server keys.

Closes #2640

There are some hacks to know the instance was run by tarantoolctl,
none of them are too reliable, though. This patch introduces 2
environment variables set by tarantoolctl for the instance to
know when it's being run or restarted.

Closes: #3215

@TarantoolBot document
Title: tarantoolctl: document setting environment variables
tarantoolctl sets the `TARANTOOLCTL` environment variable when starting
an instance, and sets the `TARANTOOL_RESTARTED' environment variable
when restarting.

Filed gh-3311 to remove this export soon.

Fixes #3310.

So that it can be used not only for serializing a list of tuples, but
also for serializing a Lua stack that stores output of CALL/EVAL.

Needed for #946

* Add struct log
* Add possibility to add logger configuration to global scope
* Refactor functions in say to use them with specified config,
 not only global variable

 This patch was inspired by need of additional logger in audit log
 Relates #2912

Improve usability.

Follow up 9297ec36 "chmod and chown control socket"

luarocks make <rockspec> allows one to build a rock from local
directory.

In addition to the "rocks make" argument, one additional option is
needed in tarantoolctl: --chdir. This is because we need to build
inside the rock directory, but output the result to
<project_root>/.rocks.

Implements #2846

* Add log_format option to box.cfg{}
* Add json format in logging
* Add table converting to json in lua logging

Closes #2795

A patch by Alexander Turenko.

Fixes #2782

Fixes #2761

queue.start() is not needed anymore.

Throw error, if a new name for a fiber in Lua is too long.

Closes #2622

* remove obsolete comments from recovery.cc
* update example lua

* update tarantool man page
* cross-reference tarantool and tarantoolctl pages

Savepoint allows to partialy rollback a transaction. After
savepoint creation a transaction owner can rollback all changes applied
after the savepoint without rolling back the entire transaction.

Multiple savepoints can be created in each transaction. Rollback to
a savepoint cancels changes made after the savepoint, and deletes all
newer savepoints.

It is impossible to rollback to a savepoint from a substatements level,
different from the savepoint's one. For example, a transaction can not
rollback to a savepoint, created outside of a trigger, from a trigger body.

Closes #2025

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

Closes #2609
Closes #2633
Closes #2616

Using %I is incorrect, because it is a result of unescaping, but
escaping never occured.
Even if we would use escaping inside tarantoolctl, it would be
inconvenient to use systemctl to operate instances.

Closes #2543

Disable background and usermode when NOTIFY_SOCKET is set.

Closes #2538

Admin console should be started before the box.cfg() call.

Closes #2079

LuaRocks requires openssl and curl in order to download
manifest from rocks.tarantool.org.

Fixes #2612

Usage:

    tarantoolctl rocks install ROCK - install a rock
    tarantoolctl rocks remove ROCK - remove a rock
    tarantoolctl rocks show ROCK - show information about an installed rock
    tarantoolctl rocks search PATTERN - search repository for rocks
    tarantoolctl rocks list - list all installed rocks

There are no other commands, options, configuration files. Our official
repository (http://rocks.tarantool.org) works out of the box. All rocks
are installed to ${PWD}/.rocks directory to support separate rocks trees
per project, as proposed by #2067. Rockspec can use "tarantool >= 1.7.x"
inside dependencies = {} block to depend on a specific Tarantool version.

LuaRocks has been slightly hacked to support custom configuration
via site_config.lua. There are no other changes in the upstream code.
It is not a fork and it isn't going to be a fork. All formats, layouts
and rockspecs are 100% compatible with the upstream LuaRocks 2017-07-10.

This feature intentionally doesn't have CMake option to disable it,
because it should be provided on all available platforms out of the box.

Other changes:

 * Add ${PWD}/.rocks to default package.path/package.cpath
 * Hack tarantoolctl to display subcommands in --help.
   Currently command line arguments handling are not perfect, but
   it can be fixed only by a new argparse implementation.

Closes #2067

A part of #1451

Since vinyl files (run, index, vylog) don't have space id, reading them
with tarantoolctl-cat fails with:

  tarantoolctl:784: attempt to compare nil with number

To match box.cfg.vinyl_read_threads introduced by the previous patch.

It should be 256Mb instead of 256Gb.

Fixes #2491

Set LimitNOFILE to 65535 to provide the best Vinyl experience
out of the box.

Closes #2465

Fiber attributes are a way to specify parameters that is different
from the default. When a fiber is created using fiber_new_ex(),
an attribute object can be specified to configure custom values for
some options. Attributes are specified only at fiber creation time;
they cannot be altered while the fiber is being used.

Currently only stack_size attribute is supported. Fibers with
non-default stack size won't be recycled via fiber pool.

API overview:

* fiber_new_ex() creates a fiber with custom attributes.
* fiber_attr_new()/fiber_attr_delete() creates/destroys attributes.
* fiber_attr_setstacksize()/fiber_attr_getstacksize() sets/gets
  the fiber stack size.
* fiber_self() returns current running fiber.

All new functions are available from public C API for modules.

See #2438

Follow up #2254

Since we've switched to Type=notify, forking isn't more needed.
Disable `background = true` in tarantoolctl to avoid potential
problems with fork detection by systemd.

Closes #2437

Force tarantool-common upgrade to support systemd notifications.

+ Add missing "s" suffix to TimeoutStartSec= option.

See #1923

On older version of systemd (systemd 219) 0 means infinity on newer
version. To make one script compatible with both versions we'll replace
infinity with 86400

error message:
```
May 11 10:09:42 jessie systemd[1]:
[/lib/systemd/system/tarantool@.service:57] Failed to parse usec_t
value, ignoring: infinity
```