Draft: Stability improvements for O-RAN FH 7.2

• library:
  • ignore if packets don't have payload instead of asserting => the gNB will show zero counters
  • do not hard code FFT size and numerology (important for FR2)
• implement #732
• update documentation:
  • describe counters
  • update NUMA spelling
  • reorganize configuration section (DPDK before gNB config because DPDK devices referenced in gnB config)
  • explain layer mapping
• patch: update to not ignore user's $(PKG_CONFIG_PATH), disable telemetry -> bumps version, need to recompile xran lib to force same version among users
• gNB
  • don't assert if PUCCH mismatches in frame/slot or activity to improve stability
  • print diagnostics if SIB1 too big for TBS

@jfiedler we should test this also rebuilding the xran lib as per the instructions (the expected outcome being that everything works as before)

doc/ORAN_FHI7.2_Tutorial.md

@@ -58,7+58,7 @@
 | Vendor                                  |
 |-----------------------------------------|
 | `oran_e_maintenance_release_v1.0`       |
 
 **Note**: the libxran driver of OAI identifies the above version as "5.1.0" (E is fifth letter, then 1.0).
 
 ## Configure your server
@@ -74,7+74,7 @@
 
 Your server could be:
 
-* One NUMA Node (See [one NUMA node example](#111-one-numa-node)): all the processors are sharing a single memory system.
-* Two NUMA Node (see [two NUMA node example](#112-two-numa-node)): processors are grouped in 2 memory systems.
+* One NUMA node (See [one NUMA node example](#111-one-numa-node)): all the processors are sharing a single memory system.
+* Two NUMA nodes (see [two NUMA nodes example](#112-two-numa-node)): processors are grouped in 2 memory systems.
   - Usually the even (ie `0,2,4,...`) CPUs are on the 1st socket
   - And the odd (ie (`1,3,5,...`) CPUs are on the 2nd socket
 
@@ -91,4+91,4 @@
 |-------------------|------------------|
 |XRAN DPDK usage    |0,2,4             |
 |OAI `ru_thread`    |6                 |
 |OAI `L1_rx_thread` |8                 |
 |OAI `nr-softmodem` |1,3,5,7,9,11,13,15|
 |kernel             |16-31             |
 
-In below example we have shown the output of `/proc/cmdline` for two different servers, each of them have different number of numa nodes. Be careful in isolating the CPUs in your environment. Apart from CPU allocation there are additional parameters which are important to be present in your boot command.
+In below example we have shown the output of `/proc/cmdline` for two different servers, each of them have different number of NUMA nodes. Be careful in isolating the CPUs in your environment. Apart from CPU allocation there are additional parameters which are important to be present in your boot command.
 
 Modifying the `linux` command line usually requires to edit the `/etc/default/grub`, run a `grub` command and reboot the server.
 
-### One NUMA NODE
+### One NUMA Node
 
-Below is the output of `/proc/cmdline` of a single numa node server,
+Below is the output of `/proc/cmdline` of a single NUMA node server,
 
 ```bash
 NUMA:
@@ -115,9 +115,9 @@ isolcpus=0-15 nohz_full=0-15 rcu_nocbs=0-15 kthread_cpus=16-31 rcu_nocb_poll nos
 
 Example taken for AMD EPYC 9374F 32-Core Processor
 
-### Two numa nodes
+### Two NUMA Nodes
 
-Below is the output of `/proc/cmdline` of a two numa node server,
+Below is the output of `/proc/cmdline` of a two NUMA node server,
 
 ```
 NUMA: