SCF222 says that dci_pdu in PDCCH PDU
(nfapi_nr_dl_tti_pdcch_pdu_rel15_t) should be an array, and not its
members.

Initially, filling the PDCCH and PDSCH nFAPI messages was split into a
separate function (in an attempt to keep the code structure similar to
LTE). However, this proved as not helpful: the nr_fill_nfapi_dl_pdu()
just filled the messages, with a parameter list almost size as long as
the actual messages (because most parameters are kind of independent).
This made no sense, so we put it back.

Also, from an understanding POV, they just fill a message as specified
in SCF222, so it should not be a problem.

- No dynamic allocation of PUCCH structures
- Use first PUCCH for HARQ (can only allocate for up to two slots in
  single PUCCH, simplistic nr_acknack_scheduling!)
- Use second PUCCH for CSI, do not multiplex!

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

Update in SIB1 implementation to solve REG to CCE mapping issues and also correction in pdcch RE extraction when BWP_start>0.

* MR 1031: LTE/NR X2AP: fix content of SgNBAdditionRequest
Wireshark (version 3.3.2) was not happy. https://asn1.io/asn1playground/ was not happy.

* MR 1036: LTE ULSCH bugfix
Minor fix in the UL scheduler

* MR 1008: NR SA ITTI sim update for core connectivity
Updates for connections to 5G core node using ITTI sim. Usage documentation have also been added.

* MR 1025: Cleanup NR RA procedure - mostly UE

Even stricter check/hack for BWP ID.
Drop every DCI where this value is not '1'.