fix non standard interface locations. (#1186)

[techtasie]

Description

Instead of relying on the broken get_interface_path function, I use the rosidl_interfaces resource directly. (see explanation)

Fixes #1186

Is this user-facing behavior change?

No

Did you use Generative AI?

No

Additional Information

For rolling, this issue will be resolved by changing the behavior of ros2idl in ros2/rosidl#935

This patch can be backported to Jazzy and humble.

I am unsure whether it is correct to fix this in ros2cli or whether the change should happen in rosidl_runtime_py. Due to the huge number of packages that depend on rosidl_runtime_py, I am hesitant to make that change there, especially since packages rarely rely on the .msg/.srv/.action files.

[fujitatomoya]

i believe that using this resource as the source of truth for lookup is much more robust than inferring paths from directory names. lgtm with green CI. i would like to have 2nd review on this before merge.

[techtasie]

@fujitatomoya, I have updated the package not found message and changed the expected test output for show test_msgs/msg/NotAMessageTypeName

[fujitatomoya]

Pulls: #1205
Gist: https://gist.githubusercontent.com/fujitatomoya/d72b90a247a7e2a3624cdee64ec40c7a/raw/8dddf41ccd11c96ca2469f1a6e264b340b3ff84d/ros2.repos
BUILD args: --packages-above-and-dependencies ros2interface
TEST args: --packages-above ros2interface
ROS Distro: kilted
Job: ci_launcher
ci_launcher ran: https://ci.ros2.org/job/ci_launcher/18593

• Linux
• Linux-aarch64
• Linux-rhel
• Windows

[fujitatomoya]

this PR requires ros2/rosidl#935 1st.