MB-100: start babysitter node with nocookie

I've seen that if I don't specify cookie then it'll generate some
sensible and randomly-looking cookie itself (but interstingly, not on
windows). So I decided to allow it to use it's own generated cookie.

But I've just found that something (presumably erlang itself) is
saving that generated cookie to /opt/couchbase/.erlang.cookie. That's
world-readable location (at least as of now) and thus is not really
secure.

Starting with nocookie will cause babysitter to generate cookie via
our normal cookie generation code.

Change-Id: Ic5e790d9ddbc4f077f210bf545985081e634695d
Reviewed-on: http://review.couchbase.org/25576
Reviewed-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
Tested-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
MB-8047: pass babysitter cookie to ns_server securely

I.e. via environment which is not world-readable. I.e. contrary to
process' argv.

Change-Id: Ia530a7bd09e766ac0b573865414ebccdd3fce7e3
Reviewed-on: http://review.couchbase.org/25577
Reviewed-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
Tested-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
MB-100: fix potential parallel make breakage

I.e. babysitter actually depends on ale's parse_transform. So we
really need to reflect that in dependencies.

Change-Id: I15505b1eb243bca81980aacbc1f403aeb4a2c5ab
Reviewed-on: http://review.couchbase.org/25578
Reviewed-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
Tested-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
MB-8046: don't make $prefix/var/lib/couchbase world-readable

I.e. because we store some sensitive stuff inside.

Change-Id: Icdd2df1e3ff37d04d4e714ddc7c34ae0d4a13802
Reviewed-on: http://review.couchbase.org/25579
Reviewed-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
Tested-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>