Fix/driver status drops

[MishkaMN]

PR Details

Description

The driver status subscriber is listening only 1 depth of msg. Typically there are minimum 4 drivers all publishing to the same topic at 10 Hz, so the subscriber can miss many status updates. This is often leading to driver timeouts although the driver is operational and publishing its status at 10 Hz fine.

Depending on the PC's specs this issue can be more pronounced.

So this PR increases the 1 depth to 20
Also added DEBUG log and cleaned some misleading return calls

Related GitHub Issue

#2186

Related Jira Key

CDAR-643
https://usdot-carma.atlassian.net/browse/CDAR-643

Motivation and Context

Integration testing VRU use case - platform is timing out due toe driver status messages being dropped over the ros1_bridge depending on the PCs

How Has This Been Tested?

Simulation PC 1

Types of changes

• Defect fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that cause existing functionality to change)

Checklist:

• I have added any new packages to the sonar-scanner.properties file
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[paulbourelly999]

Looks good