It is possible that we read less bytes then requested cause the actual
file doesn't have so much.

Mercury now support shared memory autorouting.

A single margo instance can be initialized and it will handle both
shared memory communication and remote ones.

If the endpoint of the RPC is local mercury will automatically use
shared memory.

Since there is only one margo instance all the duplicated code for
rpc/ipc have been unified and simplified considerably.

------

The way in which client contact the server has changed.

 - Server initializes its own margo instance and generate the endpoint
communication string using `HG_Addr_self`.
 - This endpoint description string is written on the pid file
 - When the client library loads it will fetch the server endpoint
description from the pid file and will use that to contact the server.

I couldn't figure out why this is happening, but the inline function
cannot be found at runtime

ensure rpc_addresses object have been initialized before we use it for
the first time

margo, argobots and mercury have been updated. The abt-snoozer dep
required by margo it is not needed anymore.

RocksDB has been also updated to the lastest release

loggers can be now configured at execution time, by using environment
variables for both server and client.

Server:
 - ADAFS_LOG_LEVEL
 - ADAFS_DAEMON_LOG_PATH

Client:
 - ADAFS_LOG_LEVEL
 - ADAFS_PRELOAD_LOG_PATH

Since we introduced the `initialized` flag in the preload context, it is
not needed anymore to check for ld_is_aux_loaded flag.
In fact ld_is_aux_loaded is true if and only if the `initialized` flag
is true.

The library intercepts IO functions from others library constructors
before our constructor have been executed.

All the interceptions triggered before that our constructor have been
executed are now forwarded to the glibc.

By moving the logger initialization outside of the passthrough
initialization we will be able to implements fopen interceptions.

Avoid the usage of a custom cmake "find-module" for mercury.
Instead use the official exported target

In the glibc both readdir and closedir functions marks the @dirp parameter
with a non-null attribute.
If we use a compiler optimization level grater then 1,
the `dirp == nullptr` expression is evaluated to false
at compilation time and the relative if blocks is cutted out
of the final binary.

In order to avoid this bheaviour, we implement a functions and then set
that as weak alias of the real glibc function call.

readdir and closedir in glibc returns a EINVAL if the directory pointer
passed as parameter is NULL

Both __xstat and __lstat simply needs to invoke adafs_stat.

Support for the following calls has been added:
 - opendir
 - readdir
 - closedir

The readdir call use the new RPC get_dirents that ask to all the
nodes (broadcast) about all the existing first-level entries
of a specific directory.

In order to support directories functionalities
opendir,readdir,closedir,etc.. the OpenDir class has been introduced.
This is a new specialization of the OpenFile class so that OpenDir
object can be stored in the open_file_map along with regular file.

Allow to add already instantiated OpenFile to the OpenFileMap.

This will come in hands when we will have sub-classes of the OpenFile.
In that case this new add function will accept all object that are
derived from the OpenFile class. See directories functionalities.

In the case the open call has been called with the O_DIRECTORY flag the
ENOTSUP (Operation not supported) will be returned.