The current pcie-fpga-driver exports the device
name with the correct slot number. So, we don't
need to rely on the FPGA and MMC to get this
information.

These were causing an error when comparing
with the string fmc130m_4ch or fmc250m_4ch.

Now, we can select between FMC130 or FMC250
within the config file.

With this, we can force the BPM to spawn
the module to control an specific FMC. For now,
supported values are "fmc130m_4ch" or "fmc250m_4ch"

On CONFIG builds, er_card_slot is not used,
but is defined. This is an error for us.

We were destroying something that could be
uninitialized. The solution was to invert
and correct the order of destruction of
objects.

This was effectively skipping compilation of
AFC Diagnostics module.

With this we have more control over a faulty
child DEVIO, for instance.

This was based on the functions available on
dev_mngr (src/dev_mngr/dev_mngr_core.c and
include/dev_io_core.h)

In fact, we need this for non AFC boards,
like ml605 which does not have AFC DIAG modules.
Thus, no addresses for AFC DIAG module exists in the
mem_layout.h file, causing the compilation to fail.

This reverts commit 05d338d3.

The conditional compilation was used before
the linker table. Now this is not necessary
and, in fact, is an error as afcv3_1 sttills needs
this module, but would not be compile with it as
just afcv3 is specified in the Makefile.

In fact, specifyng it is an error as upstart
will hang on start/stop

As all of the Malamute is a draft API, we need
this for Malamute version 1.0.0