gkfs::hg_tag -> gkfs::rpc::tag
gkfs::utils -> gkfs::util
gkfs::client -> gkfs::util
gkfs::logging -> gkfs::log

Reformatted code w.r.t. unifying code styles as of the official
CPPCoreGuidelines by Stroustrup and Sutter

Restructuring code w.r.t. configurations and definitions:
- #defines have been mostly removed from configurations
- a dedicated config file has been added for configurations with constexpr
- past configure file is now only a cmake wrapper
- wrapping global functions into namespaces

Removed all adafs and ifs occurrences. Now called gkfs

 - Use regular expression to parse lines
 - More consistent error handling
 - More comprehensive error messages

We now use getaddrinfo syscall instead of parsing /etc/hosts in order to
resolve hostnames

For some comunication layers an out of band communication is required for putting in place the specific protocol handshake.

In those case a shared lookup file could be used to distribute deamon's endpoints information to all the clients.

This file need to resides on a shared filesystem and can be specified using the new CLI parameter `--lookup-file`.

The access RPC have been removed. The POSIX access functionality now is implemented through the stat RPC. This makes code easier to maintain and modify.

There would be a little performance degradation on the POSIX access
function because we are now retrieving also the metadata
associated to the file.

This change makes a lot easier to add symlink support

 - improved statfs system call
 - intercepted statvfs library call

Both of the above function now report the aggregated real size
of all the data-nodes.

You can test this with `df "/tmp/gekkofs_mountpoint"` command

the functionality wasn't used at all and it will be implemented later
with a different approach

Some of the variables of stat struct are not initialized, thus they will
remains will unpredictable junks data from memory. This random values
could induct strange behaviours on user applications.

Even if we don't support some of the fields in the struct stat, it is
necessary to set them to some default value.

According to the glibc [1] the stat64 function family would be called only
on 32-bit machine.

To be sure we still intercept the function, but we now throw a NOTSUP
error.

In this way we can drop the adafs_stat64 function and implement just the
logic to populate the `struct stat`.

[1]: https://github.molgen.mpg.de/git-mirror/glibc/blob/20003c49884422da7ffbc459cdeee768a6fee07b/sysdeps/unix/sysv/linux/generic/xstat.c#L46

Implemented all the logic to handle truncate operation.

Test: added truncate test

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.

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

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.

The new PreloadContext class is used as singleton to store the general context
information of the interception library.

The plan is to move global accessed variables into this sigleton.

At the moment just the logger object has been moved into it.

Previously, host rpc addresses have been looked up lazily when a request
was done. This is not necessary as all hosts are looked up anyways
while the file system is running.

Now, all RPC addresses are looked up when the environment is initialized.
After that, the rpc_address map is only accessed read-only and does not
require a mutex anymore.