fix: add float() casts in ROS geometry_msgs coordinate conversion functions

[thueljules]

Summary

• ROS 2 `geometry_msgs` fields (`Point`, `Vector3`, `Quaternion`) assert that assigned values are `float`; ProjectAirSim delivers pose/position data as Python `int`, triggering `AssertionError: The 'x' field must be of type 'float'` at runtime.
• Added explicit `float()` casts on every numeric component in five functions in `utils.py`: `to_ros_point`, `to_ros_position_vector3`, `to_ros_position_list2list`, `to_ros_quaternion`, and `to_ros_quaternion_list2list`.

Test plan

• Run the ROS bridge with a live ProjectAirSim instance and confirm no `AssertionError` is raised when pose/transform data is published.
• Verify that coordinate values (including negated components like `-vector["y"]`) are correctly cast and published to ROS topics.

[LucasJSch]

This is awesome! Thanks for your contribution @thueljules 🦾

Is this already for review, or is it a WIP? Because I see the test plan's checkboxes still empty.

[thueljules]

I've run it on my side, but I thought maybe someone should try it before merge