Avoid node clashing when USE_COLLISIONCHECK is true

[Affonso-Gui]

When USE_COLLISIONCHECK tag is true node clashing occurs in hironx_ros_bridge_real.launch:

roslaunch file contains multiple nodes named [/collision_state].
Please check all <node> 'name' attributes to make sure they are unique.
Also check that $(anon id) use different ids.
The traceback for the exception was written to the log file

This can be solved by not calling collision_detector.launch, which is already included by setting USE_COLLISIONCHECK to true.

The argument is also added in hironx_ros_bridge_real.launch, so we can set it from command line.

@pazeshun

[pazeshun]

Note 1:
In our hironx, collision detector rtc (co.rtc) can be running thanks to #423 , so we want to set USE_COLLISIONCHECK to true in hrpsys_ros_bridge.launch and use CollisionDetectorServiceROSBridge.
Otherwise (setting USE_COLLISIONCHECK to false), that bridge doesn't bring up.

[pazeshun]

Note 2:
collision_detector.launch newly launches and uses collision detector rtc outside robot, while setting USE_COLLISIONCHECK to true in hrpsys_ros_bridge.launch uses collision detector rtc inside robot.

[pazeshun]

@k-okada I think this PR harms nothing. Would you please review this?

[pazeshun]

@k-okada Travis passed thanks to #531 . Please review this.