Fix deprecated hardware_interface API

[christophfroehlich]

See ros-controls/ros2_control#2323
needed for ros-controls/ros2_control#2589

Please release it to kilted and rolling, thanks :)

[gemini-code-assist]

Summary of Changes

Hello @christophfroehlich, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the dynamixel_hardware_interface to align with the current ros2_control API by fixing the usage of a deprecated hardware_interface method. The primary goal is to ensure the hardware interface remains compatible and functional with the latest ros2_control framework, specifically by modifying the on_init method's parameter type.

Highlights

• API Update: The on_init method signature in the DynamixelHardware class has been updated to use hardware_interface::HardwareComponentInterfaceParams instead of the deprecated hardware_interface::HardwareInfo.
• Compatibility Fix: This change addresses a deprecated API usage, ensuring compatibility with newer versions of ros2_control and preventing potential build or runtime issues.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly updates the on_init method to use the new hardware_interface::HardwareComponentInterfaceParams API, addressing the deprecation of using hardware_interface::HardwareInfo directly. The changes in both the header and source files are appropriate. I have one suggestion to update the documentation to maintain consistency with the API change.

[gemini-code-assist]

While the function signature is correctly updated, the corresponding Doxygen comment at line 115 is now out of sync. Please update the @param tag to reflect the new parameter name and type for better code clarity and maintainability.

For example:

   * @param params Parameters for the hardware component interface.