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.

Searching for mercury dependencies is useless. In fact if a library has not been linked and enabled while mercury was built, we won't be able to use it.

Moreover, mercury ships with a make module that provides which links flags needs to be used. Thus there is no need to search for mercury dependencies.