Recognize -w --wrapper, and don't daemonize if run from a wrapper.

 + Add tarantoolctl enter instance_name command

+ Fix logrotate.d config. #473

Don't try to execute a Lua script.

- change /etc/default format to Lua
- change defaults format to tarantool.cfg
- don't force logger/snap_dir/wal_dir/work_dir if it's set
- minor fixes in logging
- implement fio.dirname

* tarantool_ctl -> tarantool_ctl
* Add test-run on travis-ci (closes gh-221)
* Proper fiber name in the log

* In RPM/DEB we introduce new utility - tarantool_ctl (extra/dist/dist.lua)
* /var/pid -> /var/run
* Fix extra/dist/dist.lua
* /extra/dist/tarantool.init and /extra/dist/tarantool.service now
  are regenerated by cmake (paths to `dist.lua`)
* Systemd service (Uses sysv-init script)
* RPM Supports both systemd and init (by using '--with systemd' in
  rpmbuild flags)

TODO: Fedora 19,20,rawhide, CentOS 7 Uses systemd.

Split effective and granted access.
Add "role exists", "role doesn't exist" errors.
Test role create and drop.

Rename space_check_access() to access_check_space()
to follow the convention.
box.session.su('role') is not allowed

Implement box.schema.user.info() which print user's grants

gh-409: connect followed by session.su causes privilege error

The problem was in the order of access checks
for functions:
    if a user has no universal access,
        find function
        check if a user has rights to execute the function

There were no pre-created function object for
'dostring', so access check for this function failed.

The fix is to give universal access to ADMIN user
right in bootstrap.snap and remove check for ADMIN uid
as a special case from access checks.
This avoids a functio lookup which would still find nothing.

The fix revealed a race condition in replica bootstrap
(see changed replication tests):
replica begins accepting requets before fully recovering.
Add a manual check for full replica recovery to make
the tests pass.

Also - remove 0*1.snap from RPM Spec

1) Backport `path_find`
2) Disable debuginfo in RPM
3) Disable failing part of BSDSocket test