[Bug] Excess logs stored on FMU cause uxrce_dds client inconsistencies with connecting to the agent and topic ingestion

[dirksavage88]

Describe the bug

When storing a lot of logs on the fmu, for some reason the quantity and size of the logs add up and eventually cause issues with the uxrce_dds_client module.

1. The uxrce_dds_client no longer reliably connects to the agent (even with retry behavior?). For example at boot the dds client does not connect, but only after restarting the agent will the client sometimes connect (basically retry the connection)
2. Even if connected, the client does not correctly consume the /fmu/in topics. Have not tested an echo of /fmu/out but this should also be looked at

To Reproduce

1. On an fmu with clean log storage test the uxrce_dds_client connection (incoming and outgoing topics). Ensure it is nominal.
2. record logs manually or through flight tests. Accumulate at least 100 logs of varying size
3. Again test the uxrce_dds_client connection after the accumulation of logs
4. Record the results: if failures in the dds client connection, clear the logs
5. Observe the uxrce_dds client connection state after clearing the logs

Expected behavior

Log storage should not be detrimental to the uxrce_dds_client module connection state and performance

Screenshot / Media

No response

Flight Log

No response

Software Version

No response

Flight controller

FMUv6x

Vehicle type

Multicopter

How are the different components wired up (including port information)

No response

Additional context

No response