software/ors-amarisoft: Enable check-rx-saturated promise for Lopcomm Radio Unit as well

The code had check-rx-saturated under `if not ru == "lopcomm"`, but checking RX
signal for saturation is implemented on eNB side, not by RU itself, and is
RU-independent because eNB only receives raw samples from RU and decides on its
own whether those samples are higher than saturation margin or not.

As an extra proof that checking for RX saturation is meaningful for Lopcomm too here is how samples.rx data can look like in the case of 2 Lopcomm Radio Units:

    root@callbox-005:/srv/slapgrid/slappart16/var/log# cat amarisoft-stats.json.log |jq .data.samples.rx
    [
      {
        "rms": -382.3080749511719,
        "max": -382.3080749511719,
        "sat": 0,
        "count": 1221181440,
        "rms_dbm": -382.3080749511719
      },
      {
        "rms": -382.3080749511719,
        "max": -382.3080749511719,
        "sat": 0,
        "count": 1221179392,
        "rms_dbm": -382.3080749511719
      }
    ]
    ...

i.e. all the data, that check-rx-saturated promise works on, is there.

/cc @jhuge, @xavier_thompson, @Daetalus
/reviewed-by @lu.xu
/reviewed-on !1478

software/ors-amarisoft/buildout.hash.cfg

@@ -80,7 +80,7 @@ md5sum = 52da9fe3a569199e35ad89ae1a44c30e
 
 [template-enb]
 _update_hash_filename_ = instance-enb.jinja2.cfg
-md5sum = b52a8584712f9cee338c71a6dedc7dad
+md5sum = b7eb14b96936b488280c00c67db06bd9
 
 [template-gnb]
 _update_hash_filename_ = instance-gnb.jinja2.cfg

software/ors-amarisoft/instance-enb.jinja2.cfg

@@ -20,9 +20,7 @@ parts =
   check-sdr-busy.py
   check-baseband-latency.py
   check-amarisoft-stats-log.py
-{% if not ru == "lopcomm"  %}
   check-rx-saturated.py
-{% endif %}
   monitor-base
   publish-connection-information