Feature: Remove Setup Path References from Static Launch Files

[luis-camero]

1. Platform Launch File

Replaced the setup_path argument in all platform related launch files:

• description.launch.py: Now requires URDF path to be passed as argument instead
• control.launch.py: Now requires path to control.yaml instead of inferring it from the setup_path root directory, defaults to the static file, generic/empty.yaml
• localization.launch.py: Now requires path to localization.yaml, defaults to the static file generic/localization.yaml
• teleop_base.launch.py: Now requires path to both twist_mux.yaml and teleop_interactive_markers.yaml, defaults to the static file config/twist_mux.yaml and generic/teleop_interactive_markers.yaml
• teleop_joy.launch.py: Now requires path to teleop_joy.yaml
• platform.launch.py: Top level launch file now exposes all of the new arguments listed above.

2. Manipulators Launch File

Replace the setup_path argument in all manipulator launch files:

• control.launch.py: Now requires path to control.yaml, does not have a default.
• moveit.launch.py: Now requires namespace, robot_urdf, robot_srdf, and config_moveit, none have defaults.
• manipulators.launch.py: Top level launch file now exposes all of the new arguments listed above.

3. Launch Generator

Due to the launch arguments changing, the launch generator was modified to provide the new arguments in the generated launch files.