Remove most ra_ResponseWindow config options

Since the parent commit, the ra_ResponseWindow will be chosen
automatically. Correspondingly, remove most ra_ResponseWindow options
from configuration files in the repository.

One problem in some mu=1 configs is that the ra_ResponseWindow=4 (10
slots), which might be overly restrictive if the L1 slot ahead is
somewhat close to 10 (e.g., 6), in which case we might not be always
able to allocate Msg2 in time.

A notable exception here is gnb-vnf.sa.band66.u0.25prb.nfapi.conf, in
which we still provide it (1) since it uses a non-standard configuration
of a ra_ResponseWindow longer than 10ms (see also issue #916 for more
information) and (2) as an example.

doc/nfapi.md

@@ -95,8 +95,9 @@ can proceed as follows:
 - in `vnf.conf`
   * modify `MACRLCs` section to configure south-bound nFAPI transport
   * delete `L1s`, `RUs`, and radio-specific sections.
-  * in `gNBs` section, increase the `ra_ResponseWindow` by one to extend the RA
-    window: this is necessary because the PNF triggers the scheduler in the VNF
+  * in `gNBs` section, select a sufficiently large `ra_ResponseWindow` if a UE
+    does not connect with a message that the response window timed out:
+    this is necessary because the PNF triggers the scheduler in the VNF
     in advance, which might make the RA window more likely to run out
 - copy `monolithic.conf`, which will be your PNF file (`pnf.conf`)
 - in `pnf.conf`

doc/testing_gnb_w_cots_ue_resources/gnb.conf

@@ -82,9 +82,6 @@ gNBs =
 #powerRampingStep
 # 0=dB0,1=dB2,2=dB4,3=dB6
         powerRampingStep                                            = 1;
-#ra_ReponseWindow
-#1,2,4,8,10,20,40,80
-        ra_ResponseWindow                                           = 5;
 #ssb_perRACH_OccasionAndCB_PreamblesPerSSB_PR
 #1=oneeighth,2=onefourth,3=half,4=one,5=two,6=four,7=eight,8=sixteen
         ssb_perRACH_OccasionAndCB_PreamblesPerSSB_PR                = 4;