The latest bfd.h requires PACKAGE and PACKAGE_VERSION to be set.

Fix iteration over a hash index to notw return garbage tuples.

Now that the network layer is exception aware, slowly
transit with the rest of Tarantool subsistems to
exception-based error handling model.

Make sure fiber_create() throws an exception
if there is insufficient memory for fiber or its
stack. Make the rest of the code aware of the change.

Conflicts:
	test/box/admin.result
	test/box/configuration.result
	test/box/lua.result
	test/box_memcached/off.result

https://bugs.launchpad.net/tarantool/+bug/1061147

Patch contributed by Mons Anderson

When accessing Lua stack via a numeric index, first calculate
absolute value of the index.

Dont' malloc() struct coio.
It's tiny and safe (unless ev_io_start() is done) to pass
around by value.

Make all subsystems (administrative console,
replication, memcached, binary protocol) use exception-based
socket API (sio.m).

Remove all fiber members related to socket I/O.
Remove fiber->peer and fiber->cookie.
The idea of the cookie is to preserve in the WAL
the originator of the request. This information is, however,
lost when saving a snapshot. To my knowledge there is no use
of this functionality, apart from pretty-printing
the WAL.

Peer is like cookie, but is textual and is used
for logging. However, now, as long as network errors
occur outside fiber context, most of the usefulness
is lost. The only remaining case is when someone is
trying to execute a write request on a read-only port.

For all other cases, sio.m already supplies SocketError
with peer name, and this is where it's most useful.

Change a single void * pointer passed to fiber_create
to a variadic list passed to every fiber_call().

Introduce two levels of new API: sio.h (the basic
socket IO) and evio.h (libev integrated socket IO).

Start changing the code base to use the new API.
Begin with replication.m.

When we recover either from a remote source or
from local log file/snapshot, a module "apply row" function
is invoked. Up until now this function
was invoked with a single argument - the row to apply,
and there were no context which would be passed around.

This worked fine as long as fibers were "all inclusive" --
i.e. contained all possible context which a function may need.

Now, when networking API and IO handles are split from
struct fiber, they need to be passed around explicitly,
in particular, into row apply function.

Prepeare the code base for this.

Conflicts:
	test/box/lua.result

- Add support for [sS] format in box.pack (16-bit integers)
- Add support for [b] ans [s] format in box.unpack (8 and 16-bit integers)
- Fix docs

Check if the number is in the 32-bit range before converting
it to a 32-bit int, in box.pack('p'). If the number is large,
convert it to a 64-bit integer.

Make box.lua just one of the many files which can be
compiled into the server.

Fix lbox_tonumber64 to not truncate large Lua numbers (which
don't fit into 32 bit range).

Make box.fiber.id() work according to the docs.