Merge branch 'feature-34-test_framework' of https://gitlab.eurecom.fr/oai/openairinterface5g into feature-34-test_framework

The distinction common space/user space still requires some
careful examination.

clang have changed its default standard to C11 compilation and is stricter.
Ensure use of gnu89 standard to use pthread extension for --castxml-gccxml

It can't link because nas_config.c and rb_config.c was commented.

Th struct SamplesPacket is a type declaration. It is not defined
in memory and thus samplesCount can't be declared static.
Transform it to true cpp static variable class as this is c++ source.

bladerf ppa don't publish packages for Ubuntu 16.04.
There are official packages for bladerf so we use these.

It breaks apt-get remove command

Add --disable-hardware-dependency flag to avoid hardware need when compiling OAI.
For the momment it avoids to flash bladeRF hardware

libpgm-dev will add the dependency on libpgm 5.2.0 or 5.1.0 automatically
according to the ubuntu version

liblas3gf have been replaced by libblas3 on 16.04
liblas3* will be pulled by libblas-dev, so we don't need to add it to package list

This package is needed for the command add-apt-repository

Thank to Thomas Laurent for refactorize get_distribution_released

build_helper exits early on error. compilations() tells where the
compilation logs can be found after compiling it. So in case of error, it
was never displayed.
Add a log info before compiling

There are a lot of case where the build scripts fails. Despite this, the
build script happily continue to the end and tells "Successfully built
xxxx".
This fix ensure the build stops early with the first error message on the
bottom of the log.

T

I did some compilation tests using `./build_oai -s --run-group "0101*"`, all was fine.

I ran `lte-softmodem` with the sequans and let it run for a while with both
uplink and downlink UDP low throughput traffic, all was fine.

I ran some TCP tests, downlink 14 Mb/s (because the sequans does not report
a CQI of 15 but 14 maximum, so we don't go to maximum MCS, so 14 Mb/s instead
of 16) with a very clean radio (almost no error in the HARQ processes).

For uplink things are not so clean, it starts at 6 Mb/s and after a while goes
down to 2/3 Mbit/s. Lot's of errors in the HARQ processes, mostly uplink but
also downlink.

This is a both with and without T activated.

So to me it's fine.

The T tracer is a debugging tool. When it's not enabled,
it has zero impact on the processing. I think we need to
do very little tests before merging. I'll let you decide
but to me it's okay!

See merge request !36