(cherry picked from commit 243c90f647a1f97dc3a1486502dc6263b5705e39)

(cherry picked from commit 5e7eb7c94857f5765bb7f18afc7f4c748acb048b)

# Conflicts:
#	openair1/PHY/LTE_TRANSPORT/ulsch_demodulation.c
#	openair1/SCHED/phy_procedures_lte_eNb.c

Fix: eNB doesn't send RRCConnectionReestablishment message when ue context cannot be found using new rnti

Merge commit '99a003b7' into develop

Hotfix: CQI scheduling in TDD

See merge request oai/openairinterface5g!711

Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

 --> also adding TDD monolithic test at 20MHz with default scheduler
 --> putting IF4.p5 TDD scenarios with default scheduler
Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

Fix cqi_req clear timing, and schedule PUSCH when CQI has not been received for a long time in fairRR scheduler.

In TDD mode, CQI requests are not possible in special subframes (at
least for some TDD configurations, see 36.213 7.2.3 that says "a
DL subframe is valid if it does not contain a DwPTS field if the
length is less than  7680 Ts").

In the code, we simply disable CQI requests in special subframes,
no matter what the length of DwPTS.

A problem can arise if the DCI0 for a given UE are sent only in
those special subframes. In this case the UE will never report
CQI and the eNB will use low MCS for this UE, impacting performances.

Another, related, problem is when there are several UEs. There again
one UE might always get its DCI0 in special subframes and thus never
report CQI. There again, performance issues.

This commit is an attempt to improve the situation.

It does two things.

1 - tag the UE as schedulable in the function UE_is_to_be_scheduled
    if the cqi_req_timer is expired

2 - use cqi_req_timer as a criterium when ordering UEs for UL scheduling

The value chosen for the expiration of the cqi_req_timer in
UE_is_to_be_scheduled is quite high (300) because as the code is
today we may overschedule the UE for short bursts until we receive
a CQI from the UE. [TODO: fix the code properly to avoid this behavior.]

Note: the fairRR scheduler has not been analyzed and this commit may
      not fix anything in case the fairRR scheduler is used.

# Conflicts:
#	targets/RT/USER/lte-ru.c

dlsch0_harq->round is an incorrect value and dlsch re-transmission dose not work.