`ros2 service call` waits forever if QoS is incompatible with concerned server

Bug report

Required Info:

• Operating System:
  • Ubuntu 22.04
• Installation type:
  • Source Code / Rolling
• Version or commit hash:
  • https://github.com/ros2/ros2/commit/54a312b7a1a812fd3a10cf87a8fe1fb1b7148f21
• DDS implementation:
  • Any
• Client library (if applicable):
  • ros2cli (rclpy)

Steps to reproduce issue

• create service with the following QoS setting

        self.srv = self.create_service(
            AddTwoInts, 'my_add_two_ints', self.add_two_ints_callback, qos_profile=qos_profile_sensor_data)

• then call the service via ros2cli service call

root@tomoyafujita:~/ros2_ws/colcon_ws# ros2 service list
/my_add_two_ints
/parameter_blackboard/describe_parameters
/parameter_blackboard/get_parameter_types
/parameter_blackboard/get_parameters
/parameter_blackboard/list_parameters
/parameter_blackboard/set_parameters
/parameter_blackboard/set_parameters_atomically
/service_provider/describe_parameters
/service_provider/get_parameter_types
/service_provider/get_parameters
/service_provider/list_parameters
/service_provider/set_parameters
/service_provider/set_parameters_atomically
root@tomoyafujita:~/ros2_ws/colcon_ws# ros2 service call /my_add_two_ints example_interfaces/srv/AddTwoInts "a: 1
b: 2"
waiting for service to become available...
...

This does not work because internally incompatible QoS setting are detected in rmw, so that hidden topics construct services will not be able to communicate each other.

Expected behavior

• User can set the QoS via ros2 service call

Actual behavior

• User cannot set the QoS via ros2 service call

Additional information

In addition to this fundamental argument extension, it requires that user needs to be able to know what QoS setting is set on the service. So that user can set the appropriate QoS parameter to ros2 service call, but there is no such interface like get_servers_info_by_service nor get_clients_info_by_service. this could be considered as new feature and interfaces.
besides, incompatible events are implemented on publisher and subscription, not for services or clients. that said, there will be not incompatible events for QoS with services.