fix ros_gz_bridge message type for Gazebo Harmonic

[luffydod]

Description

This PR updates the message types used in ROS-Gazebo bridge nodes to properly support Gazebo Harmonic. The current implementation uses ignition.msgs.* which is for older Gazebo/Ignition versions, while Gazebo Harmonic requires gz.msgs.* as specified in the repository README.

Changes

• Updated clock bridge node in sim.launch.py to use gz.msgs.Clock instead of ignition.msgs.Clock
• Updated all message types in create3_ros_gz_bridge.launch.py, replacing all occurrences of ignition.msgs.* with gz.msgs.*
• Commented out the old message types for reference where appropriate

Testing

Tested with Gazebo Harmonic, confirming that all bridges work correctly with these changes. This ensures proper communication between ROS 2 and Gazebo Harmonic simulation.

Motivation

These changes align the code with the correct message namespace convention for Gazebo Harmonic and fix compatibility issues when using the latest Gazebo version as recommended in the documentation.

[justinIRBT]

Do you know why the build_and_test is failing on this branch?

[luffydod]

Do you know why the build_and_test is failing on this branch?您知道为什么 build_and_test 在此分支上失败吗？

I noticed the build_and_test CI failure, but it seems unrelated to the changes in this PR. Based on the error log, it might be caused by an expired GPG key in the ROS repository.

[skyegalaxy]

Do you know why the build_and_test is failing on this branch?您知道为什么 build_and_test 在此分支上失败吗？

I noticed the build_and_test CI failure, but it seems unrelated to the changes in this PR. Based on the error log, it might be caused by an expired GPG key in the ROS repository.

we're validating a fix in this PR: #242

[skyegalaxy]

Do you know why the build_and_test is failing on this branch?您知道为什么 build_and_test 在此分支上失败吗？

I noticed the build_and_test CI failure, but it seems unrelated to the changes in this PR. Based on the error log, it might be caused by an expired GPG key in the ROS repository.

ok @luffydod , we got CI passing again on our end. Can you please rebase and see if that fixes it for you?

[luffydod]

Do you know why the build_and_test is failing on this branch?您知道为什么 build_and_test 在此分支上失败吗？

I noticed the build_and_test CI failure, but it seems unrelated to the changes in this PR. Based on the error log, it might be caused by an expired GPG key in the ROS repository.

ok @luffydod , we got CI passing again on our end. Can you please rebase and see if that fixes it for you?

Thanks! I've just rebased onto the latest jazzy and force-pushed.