Make ros2 action info --verbose consistent with topic/service info

[catplotlib]

Description

Adds a --verbose / -v option to ros2 action info, matching the output style already provided by ros2 topic info -v and ros2 service info -v.

Default output is unchanged. With --verbose, each action client / server is printed as a block containing:

• Node name
• Node namespace
• Action type
• Endpoint type (CLIENT / SERVER)

QoS and type hash are intentionally omitted since they are not exposed for action endpoints (per the linked issue).
Addresses the second TODO in #1210.

Is this user-facing behavior change?

Yes. ros2 action info now accepts --verbose / -v. Previously this flag was rejected as an unknown argument.

Example (new behavior):

$ ros2 action info -v /fibonacci
Action: /fibonacci
Action clients: 0
Action servers: 1

Node name: fibonacci_action_server
Node namespace: /
Action type: test_msgs/action/Fibonacci
Endpoint type: SERVER

Without -v, output is identical to before.

Did you use Generative AI?

Yes — Claude Opus 4.7

Additional Information

• Added two CLI tests in ros2action/test/test_cli.py:
  • test_fibonacci_info_verbose — asserts the verbose block fields
  • test_fibonacci_info_verbose_count — asserts -v -c suppresses the per-endpoint block
• No changes to the default (non-verbose) output, so existing users / scripts are unaffected.
• --verbose combined with --count prints only the counts, matching the behavior of ros2 topic info -v -c.

[catplotlib]

@fujitatomoya can i get a review on this please?

[fujitatomoya]

this PR does not provide consistent format without --verbose option to print the action type just like ros2 topic info and ros2 service info do. i think this is format breaking change, but it would be nice to be consistent over the endpoint types.

how about introducing ActionEndpointInfo and call the corresponding rcl interface to get those information and client libraries such as rclpy and rclcpp call this API, including ros2action via rclpy. this is more consistent with other endpoint implementation, and all the client libraries can take advantage of this API?