Msg2 and Msg3 at gNB: check allocation before committing to Msg2
This MR improves Msg2/Msg3 handling in the following ways:
- previously, on reception of the preamble, the scheduler calculated a single Msg2 "occasion" from the Msg1 received frame/slot (using slot_ahead, i.e., L1 internals). tihs is modified to only mark once we received a preamble, and then the TX scheduler will pick it up and try to allocate Msg2, possible until the end of RA window
- Msg3 allocation was partially hardcoded, or used AssertFatal(). In this MR, we now check if Msg3 can be allocated before committing to Msg2
- various refactorings, and log improvements
closes #736 (closed)
Edited by Robert Schmidt