ROS bridge attempts to get data from sensors even if not present in settings

[mateusz-lichota]

Currently, the ROS bridge assumes that GSS and GPS sensors will always be configured in the settings, and uses hardcoded sensor names to make RPC calls, which fail if those sensors are not present in settings. This behaviour should be changed to how it works with lidar, namely, having an array of the sensors of each type and making separate publishers (potentially 0 of them) for each.

Encountered this bug when I removed the GPS sensor from settings.json and the ROS bridge started printing errors about the RPC call failing:

[fsds_ros2_bridge-23] Exception raised by the API while getting gps data:
[fsds_ros2_bridge-23] rpclib: function 'getGpsData' (called with 2 arg(s)) threw an exception. The exception contained this information: No gps with name Gps exist on vehicle.
[fsds_ros2_bridge-23] error