Changes ros_timer_init for ros_timer_init2

[Voldivh]

This PR is a follow up of rcl#1004 and should be merged after that PR is merged.

Signed-off-by: Voldivh [email protected]

[fujitatomoya]

This does not change user experience with autostart flag for rclpy, i would recommend that rclpy as the same option as a counterpart of ros2/rclcpp#2005

[emersonknapp]

Pulls: ros2/rcl#1004, ros2/rclcpp#2005, ros2/system_tests#508, #999
Gist: https://gist.githubusercontent.com/emersonknapp/f9353e435d78a1ff796a38b74eaf0547/raw/2a9e6c7645332dcc2c4a6d0fb6f7b66e6b428bb7/ros2.repos
BUILD args: --packages-above-and-dependencies rcl rcl_action rclcpp rclpy test_rclcpp
TEST args: --packages-above rcl rcl_action rclcpp rclpy test_rclcpp
ROS Distro: rolling
Job: ci_launcher
ci_launcher ran: https://ci.ros2.org/job/ci_launcher/12240

• Linux
• Linux-aarch64
• Windows

[fujitatomoya]

CI is green, see ros2/rcl#1004 (comment)

[fujitatomoya]

@Voldivh

This does not change user experience with autostart flag for rclpy, i would recommend that rclpy as the same option as a counterpart of ros2/rclcpp#2005

you are not gonna implement this at this time? maybe this would be follow-up task for rclpy?

[Voldivh]

This does not change user experience with autostart flag for rclpy, i would recommend that rclpy as the same option as a counterpart of ros2/rclcpp#2005

Taking into account the chain of PR's given this one ros2/rcl#1004 . Would it be ok if we address this comment in a different PR?