Possible merge of two separate messages in RU logfile

In looking at the RU logfiles from some recent runs of the tpstream_writing_test automated regression test, I noticed what appears to be a message that is a combination of two individual ones.

Here is a snippet from a logfile that shows an example of one type, an example of an overlapping message, and an example of the second type.

2024-Sep-23 14:57:23,5682024-Sep-23 14:57:23,568 LOG [dunedaq::iomanager::IOManager::get_sender(...) at /cvmfs/dunedaq-development.\
opensciencegrid.org/nightly/NB_DEV_240923_A9/spack-0.22.0/opt/spack/linux-almalinux9-x86_64/gcc-12.1.0/iomanager-NB_DEV_240923_A9-5\
padktgadlncej2lwzn5ot7ohnog2tij/include/iomanager/detail/IOManager.hxx:104] Creating NetworkSenderModel for uid fragments_df-01, datatype Fragment in session tpstream

2024-Sep-23 14:57:23,568  WARNING [LOG [LatencyBufferType>::data_request(...) at /cvmfs/dunedaq-development.opensciencegrid.org/nig\
htly/NB_DEV_240923_A9/spack-0.22.0/opt/spack/linux-almalinux9-x86_64/gcc-12.1.0/datahandlinglibs-NB_DEV_240923_A9-hzxx4azurnnnwpb5l\
wpey7rugisxzhfk/include/datahandlinglibs/models/detail/DefaultRequestHandlerModel.hxx:532dunedaq::iomanager::NetworkSenderModel<Dat\
atype>::NetworkSenderModel(...) at /cvmfs/dunedaq-development.opensciencegrid.org/nightly/NB_DEV_240923_A9/spack-0.22.0/opt/spack/l\
inux-almalinux9-x86_64/gcc-12.1.0/iomanager-NB_DEV_240923_A9-5padktgadlncej2lwzn5ot7ohnog2tij/include/iomanager/network/detail/Netw\
orkSenderModel.hxx:20] NetworkSenderModel created with DT! Addr: 0x7ff85842fd10, uid=fragments_df-01, data_type=Fragment
] SourceID[subsystem: Trigger id: 100] Request on empty buffer: Data not found

2024-Sep-23 14:57:23,568 WARNING [LatencyBufferType>::data_request(...) at /cvmfs/dunedaq-development.opensciencegrid.org/nightly/N\
B_DEV_240923_A9/spack-0.22.0/opt/spack/linux-almalinux9-x86_64/gcc-12.1.0/datahandlinglibs-NB_DEV_240923_A9-hzxx4azurnnnwpb5lwpey7r\
ugisxzhfk/include/datahandlinglibs/models/detail/DefaultRequestHandlerModel.hxx:532] SourceID[subsystem: Trigger id: 101] Request on empty buffer: Data not found

Reproduce the merged-message symptom using the tpstream_writing_test automated regression test and inspect the RU logfile output around the three shown message forms. Trace how concurrent log messages are written and identify what separates individual records; done means the overlapping output no longer combines two messages while the existing message types remain intact.