AIRO-1464 Add a try catch so that bad logic from one received message doesn't c…

[P3TE]

So in an ideal scenario, topicInfo.OnMessageReceived(contents); always works fine, but malformed messages or bad code means that sometimes that's not always the case. The idea behind this change is that even if topicInfo.OnMessageReceived(contents); does throw an exception, it will just move on to the next received message in the queue. Without this the Update method of the ROSConnection will exit this frame and any other waiting messages will be forced to wait for the next frame. If you have some bad actor that throws an exception every frame, you could have an unbounded queue size and messages will never get received.

Provide any relevant links here.

Types of change(s)

• Bug fix/workaround
• New feature
• Code refactor
• Documentation update
• Other (please describe)

Testing and Verification

Please describe the tests that you ran to verify your changes. Please also provide instructions, ROS packages, and Unity project files as appropriate so we can reproduce the test environment.

Test Configuration:

• Unity Version: [e.g. Unity 2021.2.0b13]
• Unity machine OS + version: [e.g. Ubuntu 18.04]
• ROS machine OS + version: [e.g. Ubuntu 18.04, ROS Melodic]

Checklist

• Ensured this PR is up-to-date with the dev branch
• Created this PR to target the dev branch
• Followed the style guidelines as described in the Contribution Guidelines
• Added tests that prove my fix is effective or that my feature works
• Updated the Changelog and described changes in the Unreleased section
• Updated the documentation as appropriate

Other comments

[peifeng-unity]

I am going to merge this PR to external-intermediate branch first because Yamato cannot be triggered from an external forked repo.

[peifeng-unity]

Will merge this PR and create a new one from external-intermediate to dev.