Provide a default instance in the installation script, but don't
start it.

Now that we have a very nice title, don't use a custom proc title that
often.

Follow up fixes.
Signature changes for txn_commit_stmt(), move the check
for secondary keys to be engine-agnostic.

*)also fixed delete via secondary key
*)moved xlog creation from txn_begin_stmt to txn_commit_stmt

Do not override logger: tarantoolctl picks sensible defaults.

Remove custom proc title: script name is now included in the proctitle
automatically.

tarantool script.lua <status>: custom proc title

Accept MP_STR *and* MP_BIN as type for authentication scramble key
in IPROTO_AUTH packet.
Some codecs automatically pack non-utf-8 strings as MP_BIN. A scramble
is just an octect stream, so can (by chance) be both a utf-8 stream
and a binary stream, depending on the random seed.

Conflicts:
	doc/sphinx/reference/fiber-ipc.rst

Conflicts:
	doc/sphinx/book/box/triggers.rst

proctitle.c: since it's now fully rewritten by us, move from third_party
process_title.c: rename to title.c

Style changes.

 * Show instance name instead of 'tarantoolctl';
 * instance can set custom proc title on its own discretion.

 * add proctitle.h;
 * add config-time detection of setproctitle() syscall;
 * fixing program_invocation_(short)?_name globals (glibc);
 * fixing progname (getprogname(), initialized with argv[0]);
 * this module now works on osx;
 * fix osx ps displaying garbage (argc-1 extra \0 necessary);
 * general refactoring;
 * fix linux proctitle truncation (init_set_proctitle was called with
   argv+1, this is wrong);

 * CAVEAT: 'progname: ' prefix no longer present, will fix later

Heading style suggestion:
Fix overlapping (e.g. http://tarantool.org/doc/getting_started.html#starting-another-tarantool-instance-and-connecting-remotely)
Proper margins

Codeblock style suggestion:
Add greyish background for inline code
Add background for bash codeblocks
Add overflow property for bash codeblocks:

Add horizontal scrolling for text in code-blocks

Fix multiple issues listed in #1033 (Database section):
Addressed style inconsistency
Fixed module descriptions
Added hotlinks for functions
Minor style additions

Fix formatting issues in Reference Manual

Fix Lua code highlighting

A rather blunt fix that offers a temporary workaround.
The reason behind original Lua lexer not highlighting Lua code is '!' used as
delimiter. Pygments fails to parse '!' as a Lua code entity and tells Sphinx to
leave the code unhighlighted. The fix adds custom Lua lexer by alias 'lua_tarantool',
with '!' added as a punctuation token (line 60 in LuaLexer.py). A proper fix would
probably be to extend the lexer with all Tarantool extensions over standard Lua modules.
Lua code block directive now should be used like this:

.. code-block:: lua_tarantool

	lua code

Fix remaining problems from #1033

Review styles for Terminal session and inline code

Improve formatting for C API

Improve formatting in Lua tutorial