Make the pose_V to TFMessage conform with ROS2

[teyssieuman]

🦟 Bug fix

The conversion from a gz::msgs::pose_V message to a ros2 geometry_msgs::msg::TransformStamped message what not compatible to make it a proper "tf2" message.

Summary

Checklist

• Signed all commits for DCO

[azeey]

I'm not sure why this PR is needed. The child_frame_id is properly handled by the conversion from gz::msgs::Pose to geometry_msgs::msg::TransformStamped in

ros_gz/ros_gz_bridge/src/convert/geometry_msgs.cpp

Lines 251 to 257 in 21d4c23

	for (auto i = 0; i < gz_msg.header().data_size(); ++i) {
	auto aPair = gz_msg.header().data(i);
	if (aPair.key() == "child_frame_id" && aPair.value_size() > 0) {
	ros_msg.child_frame_id = frame_id_gz_to_ros(aPair.value(0));
	break;
	}
	}

and the frame_id is handled in

ros_gz/ros_gz_bridge/src/convert/std_msgs.cpp

Lines 171 to 176 in 21d4c23

	for (auto i = 0; i < gz_msg.data_size(); ++i) {
	auto aPair = gz_msg.data(i);
	if (aPair.key() == "frame_id" && aPair.value_size() > 0) {
	ros_msg.frame_id = frame_id_gz_to_ros(aPair.value(0));
	}
	}

[ahcorde]

not sure about this, maybe we should be able to configure this with a parameter, @azeey or @mjcarroll thoughts?