fix(nfapi): align Aerial FAPI 10.04 packing

[mud-the-developer]

Summary

This fixes the Aerial nvIPC/FAPI packing used by the gNB VNF when interoperating with NVIDIA Aerial cuPHY builds that use the SCF FAPI 10.04 layout.

The patch addresses three wire-format mismatches observed on the Aerial L2/L1 boundary:

• Do not add an extra 8-byte FAPI header length to the P5 nvIPC message length. fapi_nr_p5_message_pack() already returns the complete packed FAPI message length, including the FAPI header.
• Convert CONFIG.request TLV headers from tag:u16 + length:u16 to the SCF FAPI 10.04 tag:u16 + length:u32 format for the Aerial nvIPC boundary.
• Pack the Aerial/SCF FAPI 10.04 additions for P7 messages:
  • DL_TTI.request: testMode byte between Slot and nPDUs
  • TX_DATA.request: cw_index byte after PDU_index
  • TX_DATA.request TLV lengths as 32-bit values under ENABLE_AERIAL

Validation

• git diff --check
• Independent code review of the two-file diff for local/debug-only leftovers, security issues, and memory-safety regressions
• DOCKER_BUILDKIT=1 docker build --target oai-gnb-aerial --tag oai-gnb-aerial:pr-aerial-scf-fapi --file docker/Dockerfile.gNB.aerial.ubuntu .

Notes

This was validated on an Aerial-enabled gNB build path. The conversion is intentionally limited to the Aerial L2-to-L1 CONFIG.request nvIPC boundary so the generic FAPI packer layout remains unchanged.