0.3.2 broke our robot

[Timple]

Describe the bug
Node get's stuck:

[ros2_control_node-2] [INFO] [1770016923.647346993] [drive_right]: eds file /path/to/install/my_pkg/share/my_pkg/config/my_eds.eds
[ros2_control_node-2] [INFO] [1770016923.647365731] [drive_right]: bin file /path/to/install/my_pkg/share/my_pkg/config/drive_right.bin
[ros2_control_node-2] [INFO] [1770016923.675384371] [drive_right]: Starting with event mode.
[ros2_control_node-2] [INFO] [1770016923.675469035] [drive_right]: Starting with diagnostics enabled.
[ros2_control_node-2] [INFO] [1770016923.675552940] [device_container]: Initialisation successful.
[ros2_control_node-2] [INFO] [1770016923.675666805] [resource_manager]: Successful 'configure' of hardware 'hexxabot_system'
[ros2_control_node-2] [INFO] [1770016923.675686348] [resource_manager]: 'activate' hardware 'hexxabot_system' 
[spawner-3] [INFO] [1770016923.858471883] [spawner_joint_state_broadcaster]: waiting for service /controller_manager/list_controllers to become available...

To Reproduce
Do not have an effort PDO configured and try any commit after f3e435d

Expected behavior
Having an effort interface is great, having it suddenly required: not so great

Logs

Setup:

• Device: Nanotec CL4-E-2-12
• OS: ubuntu 24.04
• ROS-Distro: jazzy
• Branch/Commit: Before and after f3e435d

Additional context
Adding

        - {index: 0x6077, sub_index: 0}  # Torque actual value

To the bus.yml made everything operational again.
I think the issue was timing releated as suddenly the effort was polled via SDO's?

Tagging @synsi23b and @ipa-vsp as commit authors.

[ipa-vsp]

Hi @Timple, I have created #409 to address this issue.

[Timple]

Thank you!