- generic: mme_list and amf_list are now required to be explicitly set
- generic: plmn list for 5G is now configured via plmn_list_5g.
           plmn_list    is now required to be set when there are LTE cells
           plmn_list_5g is now required to be set when there are NR  cells
- generic: exposing measurment config is left as TODO
- generic: rework how defaults are handled - they are now started to be kept
           centralized in instance-enb head with TODO to load them from json
           schema.
- fix/rework gtpu computation
- fix more tojson usage to avoid issues wrt buildout
- misc ...

when serving symlinks via raw, lab returns link content (= readlink),
not content of the target.

- more B quotes
- Inter-RAT HO fixup
- robustify behaviour when no RU is configured

Else enb treats args="" unset and implicitly uses /dev/sdr0 by default.

We do not want implicit default behaviour -> we want to see an error.

In 536b892c I've made a thinko: the documentation on Amarisoft says(*) that
if those parameters are not given, their values are taken from the
"serving cell". With that and after reading https://www.telecomhall.net/t/changing-allowedmeasbandwidth/13045,
especially https://www.telecomhall.net/t/changing-allowedmeasbandwidth/13045/5 I've
made the conclusion that if allowed_meas_bandwidth, and similarly
antenna_port_1, are not provided, they will be extracted by UE from MIB
of that peer serving cell.

But I was wrong as eNB does not start if allowed_meas_bandwidth is not
given for eautra-kind handover in NR cell.

So after checking things in 36.331 we see that:

allowed_meas_bandwidth is optional only in SIB3 (Intra Frequency Cell
Reselection), but in SIB5 (Inter Frequency Neighbour Cell) it is
mandatory, and that is the reason for why enb was complaining about that
missing for NR->LTE handover.

-> restore allowed_meas_bandwidth and antenna_port_1 in HO config.

For intra-eNB HO things are clear, but for inter-eNB HO use conservative
values and put a TODO for considering to extend peer/cell/lte schema
with .allowed_meas_bandwidth and .antenna_port_1 . I think keeping the
schemas minimal is better for now until we really need to do inter-RAT
HO in practice.

(*) https://tech-academy.amarisoft.com/lteenb.doc#prop.ncell_list.allowed_meas_bandwidth

* master:
  recipe/check_parameter: support multi lines values
  software/erp5/test: use short partition references
  stack/erp5: rename an internal parameter still mentioning apache

This reverts commit 5a45624b.

These partition references should be kept short, they are a mechanism
to use a short path for unix sockets, because unix socket paths can not
exceed 108 characters.

When running the test in theia, this was causing errors:

   # [ALERT]    (100453) : config : parsing [/srv/slapgrid/slappart15/srv/runner/instance/slappart7/tmp/inst/with-max-rlimit-nofile6/etc/haproxy.cfg:37] : log : socket path '/srv/slapgrid/slappart15/srv/runner/instance/slappart7/tmp/inst/with-max-rlimit-nofile6/var/run/log.sock' too long (max 97

1) get generic tests into shape

2) fix instantiation when refrences contain spaces and/or other special characters.
   link to discussion: kirr/slapos@d5d4f7c8 (comment 196869)

3) fix schemas:
   * ru: mac_addr becomes common CPRI property instead of being Lopcomm-specific
   * ue/cell/nr: ssb_nr_arfcn is fixed to be optional, similarly to cell/nr