Unhandled MPI_Requests generated by mpi_process_group constructor.

The `boost::graph::distributed::mpi_process_group` class spawns some non-blocking communication in its constructor, but the resulting requests are never handled. I have tracked this down to the `global_trigger_launcher`, which has the following comment:

```
// TBD: do not forget to cancel any outstanding Irecv when deleted,
// if we decide to use Irecv
```

It looks like this was never done, but the default build configuration uses Irecv. To replicate this bug, simply create an mpi_process_group with any constructor, do nothing with it, and let it go out of scope. You will need some way to interact with the MPI profiling interface to detect leaked requests, such as LLNL's mpileaks:

https://github.com/LLNL/mpileaks

Inizia con il costruttore distribuito di mpi_process_group e l’implementazione di global_trigger_launcher menzionata nell’issue. Riproduci il caso di uno scope vuoto con il profiling delle MPI requests, come LLNL's mpileaks, quindi traccia le requests non bloccanti create dalla configurazione Irecv predefinita. Il lavoro è completato quando la distruzione di un mpi_process_group non lascia alcuna MPI request in sospeso.

Scritto dal modello di indicizzazione a partire dal testo della issue.