Fix ros_gz_bridge parameter_bridge command syntax

[Shivam-Bhardwaj]

Summary

Fixes the ros_gz_bridge parameter_bridge command in the Gazebo tutorial.

The command was using [ instead of @ as the separator between ROS and Gazebo message types:

- ros2 run ros_gz_bridge parameter_bridge /lidar2@sensor_msgs/msg/LaserScan[ignition.msgs.LaserScan
+ ros2 run ros_gz_bridge parameter_bridge /lidar2@sensor_msgs/msg/LaserScan@ignition.msgs.LaserScan

The incorrect syntax causes a "bad pattern" error.

Fixes #3761

[ahcorde]

This should work, check this https://github.com/gazebosim/ros_gz/blob/humble/ros_gz_bridge/src/parameter_bridge.cpp#L36-L38

[gavanderhoorn]

@ahcorde: perhaps #3761 (comment) is a better explanation of when/why it doesn't work.

It's a localised issue: when using Zsh as a shell, the bridge configuration string is interpreted as a regex/special character.

Just changing it to @ is not a proper solution though.

---

Edit: perhaps quoting using single quotes would already fix the issue? I haven't tried.

[kscottz]

Per waffle, @azeey can you take a look at this?

[azeey]

This change creates a bidirectional bridge, but that is not necessary. The original version should work as is and bridges data from Gazebo -> ROS. Looking at #3761 (comment), I think the best otion is to wrap the whole thing in single quotes

Suggested change

	$ ros2 run ros_gz_bridge parameter_bridge /lidar2@sensor_msgs/msg/LaserScan@ignition.msgs.LaserScan --ros-args -r /lidar2:=/laser_scan
	$ ros2 run ros_gz_bridge parameter_bridge `/lidar2@sensor_msgs/msg/LaserScan[ignition.msgs.LaserScan` --ros-args -r /lidar2:=/laser_scan

[dlanov]

This PR appears stale, and the reviewer feedback suggests preserving the original Gazebo -> ROS bridge syntax while quoting the bridge argument to avoid Zsh glob parsing. I can open a small replacement PR for that approach if that would be helpful.