Provide open_memstream() implementation for system which
miss it (Mac OS X).

Store the information about spaces in a pre-recreated
system space.

https://blueprints.launchpad.net/tarantool/+spec/space-ddl

Remove space configuration from confetti.
Use transaction and space triggers to run post-DML
actions to perform DDL changes.

Implement a Lua FFI binding to disable tests.

Temporarily disable space-loading code in tarancheck
and tarantar (this breaks them).

Mostly all tests are broken.
Memcached is disabled (non-functional).

Integrate libyaml instead of internal yaml formaters.

changelog:
* fixed i64 convertion bug
* refactored bindings to new admin .info() scheme
* moved lua plugin api to separate file
* moved lua fiber api to separate file
* slab binding refactored
* added fiber lua bindings
* rewriten admin reply handler
* proper yaml end-of-document formater
* proper server error formater
* fixed bug with leftover data on stack on exception error
* added support of i64 types to lyyaml
* removed couple of box.show_ bindings
* console client fixes to support new scheme

This push has a yet broken test's.

Rewrite --init-storage to dump a compiled-in blob
instead of firing off the entire save snapshot machinery.

This should simplify bootstrap in presence of system
spaces:
there's going to be no need to implement the
code which creates system, they will be created
simply by recovery from a snapshot.

Two significant changes (both arguable, since this patch is about
taste by a large measure):

1) Split tuple_seek() into two: tuple_rewind()
and tuple_seek().

tuple_rewind() simply initializes the iterator and
sets it to 'before-first' position.
tuple_seek() returns a field, and sets the iterator
to the position after the returned field.

Previosly there was only tuple_seek(), which required
tuple_next() to get the field, and it was confusing whether
or not tuple_next() after tuple_seek() is required.
Indeed, the very code I chagned sometimes would
call tuple_next() after tuple_seek() and sometimes would not.

2) Move the return value of the iterator outside
of iteration state.

The advantage of "binding" the out parameters of the iterator to
iterator state is that you bind once, and don't need to supply out
parameters into every call to tuple_next() function. It also makes
it easy to add extra out parameters for bind in the future (field
data type, flags, etc).

This makes "binding" technique popular in database driver
APIs. Binding makes API more stable, which is also
important in drivers.

In this case, however, binding adds for extra lines of code
and (possibly) few extra instructions. Plus, since
this is an internal API which we can change any day,
its stability is not as important. So it seems that for
now we're better of with an API which is a bit
more concise/efficient, and can switch to using binding later,
if needed.

Don't load corrupted tuples.

g++ (not gcc) works correctly when dealing with
extern __inline and __extern_inline constructions, thus
this hack is not necessary now.

The patch which removes the CPack-generated spec
and adds a proper spec for client, server and library
was done by Dmitry Simonenko.

Hand-port the patch to the master, since it's gone too
far away from the origin and merging it ends up in a mess.

Code review of cjson branch by Dmitry E. Oboukhov.
Hand-picking the changes since the original branch
is based on import of lua-cjson into Tarantool
revision tree, and this branch is based on a git
submodule.

This patch implements
https://blueprints.launchpad.net/tarantool/+spec/lua-cjson

This messes the old "core/module" paradigm quite a bit, but Box,
while a neat name, was confusing people.

tarantool_box is preserved as the daemon name.