Expect rmw_service_server_is_available to ret RMW_RET_INVALID_ARGUMENT

[christophebedard]

ros2/rmw#277 changed the rmw_service_server_is_available() API documentation to indicate that it returns RMW_RET_INVALID_ARGUMENT if node, client, or is_available are NULL. However, this wasn't the case in practice in the implementations of rmw_service_server_is_available() or in the relevant test.

Change the test here to expect RMW_RET_INVALID_ARGUMENT.

Required rmw implementation PRs:

• Make rmw_service_server_is_available return RMW_RET_INVALID_ARGUMENT rmw_cyclonedds#496
• Make rmw_service_server_is_available return RMW_RET_INVALID_ARGUMENT rmw_fastrtps#763
• Make rmw_service_server_is_available return RMW_RET_INVALID_ARGUMENT rmw_connextdds#150
• (rmw_zenoh already returns RMW_RET_INVALID_ARGUMENT in this case)

[christophebedard]

CI with this and the 3 rmw PRs:

• Linux
• Linux-aarch64 (excludes rmw_connextdds_common)
• Windows

[fujitatomoya]

@sloretz i do not have permission for cyclone and connexdds, can you merge all 4 PRs together?