Add rosbag processing service

[adev4a]

PR Details

This PR adds an additional service to the telematics tool to parse and rosbags and push the deserialized data to a configured influxdb bucket. Requests to process the rosbag are received from the telematics web ui through NATS. The service is configured with the required authentication parameters to influxdb, nats url and the directory where the rosbags will be stored. When the service is launched in AWS EC2, the configured directory to read from will be the mounted S3 volume. On a local deployment, the parameter will be set to the directory where the web-ui is uploading the rosbag.

The service also requires connecting to a mysql database to update entries for each rosbag being processed. This functionality will be added as a separate enhancement. Currently TODO comments are added as placeholders.

Description

Related GitHub Issue

Related Jira Key

https://usdot-carma.atlassian.net/browse/WFD-503

Motivation and Context

How Has This Been Tested?

Types of changes

• [ ] Defect fix (non-breaking change that fixes an issue)
• [x] 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.
• [x] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [ ] All new and existing tests passed.

[adev4a]

CI needs to be setup on this package once the implementation is complete

[dan-du-car]

Can we add a README.md to describe this new service and how to build this service and run tests in host machine?

[dan-du-car]

Can we rename this folder to be consistent?

[adev4a]

Can we rename this folder to be consistent?

Will do this as a last step so we don't lose tracking on the comments