review of PHY_Config_t structure parameters for FAPI-like approach. Implement the FAPI required parameters and adding some extras in separate structure. Code compile

Merge branch 'develop-nb-iot-mac' of https://gitlab.eurecom.fr/oai/openairinterface5g into develop-nb-iot-mac

Sincronization with Nick work

Implementation of configuration data structures following FAPI-like approach. Some parameters seem to be non implemented in FAPI (for the moment addedd manually). Cleaning of some part of RRC code. Code compile.

Added new files for IF-module purposes (still to complete), review some configuration procedure for FAPI-like approach. Code compile

Merge branch 'develop-nb-iot-mac' of https://gitlab.eurecom.fr/oai/openairinterface5g into develop-nb-iot-mac

Sincronization with NICK work on the same branch

First implementation of FAPI-like P5 configuration for the PHY layer. PHY_Config_t structure, modified NB_rrc_mac_config_req_eNB for triggering the IF_Module PHY_config_req function. Some common config. and all the dedicated configuration are missed

Merging mac branch to RRC branch for IF-Module implementation(still not completed). Solve some bugs. Now move to mac branch for continue implementation

Conflicts:
	openair1/PHY/impl_defs_lte_nb_iot.h

adding PHY_Config structure for FAPI-like PHY configuration, still to finish the function call. The code compile

develop_integration_w22 into develop

Summary of changes:
- UE:
  * TDD multiplexing
  * TDD autotest
  * bug fixes: power control management for Msg3, logging
- eNB:
  * CCE allocation fixes
  * S1U port in some configuration files set to 2152 (was 2153)
- support for RedHat enterprise linux 7 and derivatives (CentOS, ...)
  (work provided by RedHat)

See merge request !198

Merge remote-tracking branch 'origin/feature-143-support-enterprise-linux-7' into develop_integration_w22

Signed-off-by: Frank A. Zdarsky <fzdarsky@redhat.com>

- rename UE_NO_LOG to DISABLE_LOG_X
  because the name is misleading. The full software
  is impacted, not only the UE part
- same for compilation option ---ue-no-log
  that becomes --disable-log
- keep LOG_X for the standard case, that is the
  case without DISABLE_LOG_X where printf has been
  put. Two reasons:
  * printf is not realtime friendly
  * keep behavior similar for other users who may
    be troubled by different logs that don't add
    any benefit to previous logs