(HrpsysJointTrajectoryBridge) ros cpp style macro applied.

**DO NOT MERGE YET**.

Applying [ROS_Format.xml](http://wiki.ros.org/IDEs#Auto_Formatting) on eclipse. 

However, [CppStyleGuide goes like this](http://wiki.ros.org/CppStyleGuide#What_about_all_this_non-conforming_code.3F)
```
A lot of ROS C++ code was written prior to the release of this style guide. Thus, the codebase contains a lot of code that doesn't conform to this guide. The following advice is intended for the developer working with non-conforming code:

    All new package should conform to this guide.
    Unless you have copious free time, don't undertake converting the existing codebase to conform to this guide.
    If you are author of a non-conforming package, try to find time to update the code to conform.
    If you are doing minor edits to a non-conforming package, follow the existing stylistic conventions in that package (if any). Don't mix styles.
    If you are doing major work on a non-conforming package, take the opportunity to re-style it to conform to this guide. 
```

So it's OK if we don't want `rtmros_common` to conform to the rule.

If we decided to conform, I'll keep applying the rule to the rest of `hrpsys_ros_robotics` package and add to this PReq.