Fix conf_reload init_per_suite/1

It was using ejabberd_config_file_utils module that was renamed to
ejabberd_node_utils.
use all tests suites (sort them alphabetically)
define common and generic item counters

to be used from tests (as an example offline count from sm_SUITE)
check server purity after suite

print warning message if the state is not clean
use escalus from branch travis-full-spec
clean last_activity after anon user

this should be cleaned by anonymous_purge_hook
but after this hook there is unset_presence_hook run
which sets the last_activity info back...
manually clean last_activity after user connected over BOSH
check carboncopy purity
check registered users count after suite
lowercase username before setting last info manually
check vcard count for ldap backend
clean roster after unregistered user
register only used users in s2s_SUITE
wait for bosh client to be closed
divide ct_tty_hook into two separate modules

ct_tty_hook preserves the original behaviour
ct_mongoose_hook is meant only for mongoose and does server purity check
  and prints on server side suite/group/case starting/finishing events
makes ejabberd_node_utils more flexible