*) added stress test for snapshotting
 *) moved finalizers.test.py to long_run

test-run udpated

set test-run module in gh-3 branch for review

Conflicts:
	include/fiber.h
	include/mutex.h
	src/admin.cc
	src/admin.rl
	src/box/box_lua.cc
	src/box/request.cc
	src/box/txn.cc
	src/coeio.cc
	src/coio.cc
	src/fiber.cc
	src/ipc.cc
	src/iproto.cc
	src/log_io.cc
	src/lua/bsdsocket.cc
	src/lua/init.cc
	src/lua/session.cc
	src/memcached-grammar.cc
	src/memcached-grammar.rl
	src/memcached.cc
	src/recovery.cc
	src/replica.cc
	src/replication.cc
	src/say.cc
	src/session.cc
	src/tarantool.cc
	src/util.cc

Rename global `fiber` into `fiber_ptr`

Rename global `fiber` into `fiber_ptr` (for use with gdb and avoidance of ambiguity with `struct fiber`)

1. Enable background=false for test-run
2. Check local directory for config

Conflicts:
	src/module/mysql/mysql.cc
	test/module/net_sql.mysql.result
	test/module/net_sql.mysql.test

Backport fix from tarantool/mysql by Anton Reznikov

Implement box.once().

Right now there is a race in box.once(), this is somethign we'll
need to fix when we have master election on simultaneous bootstrap.

The patch merely "establishes" the syntax which is going to work
most of the time.

When handling join, an error from box_on_cluster_join()
was ignored and not sent to the client, so the client
believed that the JOIN was handled successfully and proceeded
with SUBSCRIBE.

Before sending OK to join, execute box_on_cluster_join(),
if it fails, the client sees an error and stops.

Make ER_REPLICA_MAX a logged error.

No test case since the test requires a fail-stop test of the replica,
which is clumsy in our framework.

Don't log exceptions of dead joinable fibers - it will
be logged by the caller, so avoid double logging.

recover_remaining_wals() is now more like an iterator,
vclockset_match() is only called when there is no current WAL.

Add a test case for gaps in LSNs.

Remove the code which existed at times when we weren't
running everything inside an event loop, so required
alternative ways of signal handling in and out of an
event loop.

Reset signal handlers when handling fatal signals,
to avoid an infinite loop.

In panic_on_wal_error=true mode, we only skip ClientError errors,
but not SystemError errors. An error to allocate a tuple is
a recoverable error, so use ClientError for it. This way,
at recovery, tuples which can't be allocated are skipped.

io replaced with fio

Add a directory watcher, in addition to the file watcher.

Chagne wal_dir_rescan_delay default value to 2, since now it's
merely a backup.

When a new log file is created, replication relay may notice
and try to open it before it has a valid header. In this case
the relase is lead into believing that the log file is corrupt.

When opening a new xlog file, first create the file with .inrpogress
suffix, then write the header, thus get a good file, and only then
rename it to a name without a suffix, so that it's noticeable by
the relay. This prevents sporadic failures of replication with
message "failed to read log file header".

The problem was spotted in Avito after a recent upgrade.

Conflicts:
	test/box/sql.result
	test/box/sql.test.lua