Add ROS 2 Launch System + Documentation

[stex2005]

Closes #136

Completed Tasks:

• Analyzed current script - Identified all functionality in launch_ros.sh
• Created ROS2 launch files - Replaced shell script with proper launch files:
• ros_mcp_rosbridge.launch.py - Rosbridge only
• ros_mcp_turtlesim.launch.py - Turtlesim only
• Updated documentation - Created comprehensive launch system guide

Key Improvements:

• Proper process management with automatic cleanup
• Configuration options via launch arguments
• ROS2 integration with standard ros2 launch command
• Better logging and error handling
• Modular design for different use cases

Usage Examples:

The new launch system provides better reliability, easier maintenance, and proper integration with ROS2 tooling compared to the manual shell script approach.

Ready for Review ✅

[rjohn-v]

Does this file have any benefit over directly running
ros2 launch rosbridge_server rosbridge_websocket_launch.xml ?

Having a python file makes sense when launching multiple nodes at once (like with turtlesim), of course.

What is the issue that this file is trying to address?

[stex2005]

The idea is that:

• it incorporates within the launch file information about the ip/port of the rosbridge (defaul 127.0.0.1:9090).
• it manages more gently startup/shutdown.
• it creates a baseline for running rosbridge with other nodes, some sort of template launch.py
• it is easier to find and users don't have to remember the specific command: ros2 launch rosbridge_server rosbridge_websocket_launch.xml

Can be removed if not needed.

[rjohn-v]

What is the intended audience for this instruction file?

Specifically the line "The ROS-MCP Server uses proper ROS2 launch files for process management." is a bit confusing since the ROS-MCP server does not explicitly need to use any launch files at all.

They are useful tools in the examples and tutorials, and having good, modern launch files for these is valuable. But do we need a document telling users of the MCP server about why we chose certain launch systems for the examples?

[stex2005]

It's a guide that provides template launch files for developers to integrate their robots with the ROS-MCP Server. These templates demonstrate how to combine your robot's existing launch files with rosbridge for MCP communication.

Future Vision: As rosbridge becomes a standard ROS node, the ROS-MCP Server itself will be launchable through ROS2 launch files, making integration even more seamless.

[stex2005]

Ready for Review ✅

[stex2005]

Closes #136