UPDATE: read the comment below, this MR will be remade completely

One of our client is an operator who wants to use ors-amarisoft for a 3-sector cell site. They want us to match exactly their enb.cfg configuration. Their configuration is one they are already using on a Amarisoft BBU not handled by ors-amarisoft SR, it is a configuration tailored for their operator needs which supposedly includes optimization and fine-tuned values for their case. The changes are located in the following parts:

• mme_list
• the cell description in cell_list
• new SIB: sib4, sib5, sib6, sib7, with sib5 being different for each cell
• drb config
• ncell_list

The client has pre-defined parameters for each frequency, so when he puts a certain frequency in a cell in the input parameters he wants other parameters to be automatically set (such as n_antenna_ul, n_antenna_dl, bandwidth...).

For ncell_list the client wants to set different neighbours for each cell.

This patch adds an boolean input parameter "top_config" for each cell, if this parameter is present then the parameters for the cell and corresponding RU are updated to the predefined parameters.

I have tested that this code generates the wanted configuration on a test machine, but have not yet tested it with a test suite, which is why I am putting WIP. I will make sure the test pass as soon as I have time to work on this again, but I don't think we are in a hurry to merge this. Also I think to do things properly we should make a new shared software type where we put the pre-defined paramters instead of putting them in a dictionnary in slaplte.

/cc @lu.xu @kirr @tomo