Address rcl API change and uninitialized rosidl sequence fields

[David-LP99]

Description

This PR aims to update the rolling branch fixing issues that appeared due to changes in other repositories.

Main changes:

• Changes to be compatible with the rcl API changes from Add API for client libraries to set action server goal expiration callbacks rcl#1295.
• Fixes segfault caused by the new is_rosidl_buffer/owns_rosidl_buffer fields that Update rosidl cpp path to emit rosidl::Buffer for uint8[] type rosidl#942 added to primitive sequences, which hand-built sequences left uninitialized

Is this user-facing behavior change?

Did you use Generative AI?

Claude Code Opus 4.5 was used in the investigation and resolution of this issue.

Additional Information

Some micro-ROS demos and application don't work with the latest version of rolling without these changes.

[christophebedard]

Today's scheduled CI job failed (https://github.com/ros2/rclc/actions/runs/36434963468/job/108970377166#step:6:488) and CI passes for this PR, so LGTM.

However, the Rpr job is required to merge the PR, yet it isn't triggered because of an issue with GitHub. IIUC, we need to delete the hook and recreate it, but I personally don't have the permissions to do it

[christophebedard]

@ros-pull-request-builder retest this please

[christophebedard]

@clalancette I think we also need to remove the requirement on Rpr__rclc__ubuntu_noble_amd64, because we've moved to Resolute. So I assume the job name won't be the same

[clalancette]

@clalancette I think we also need to remove the requirement on Rpr__rclc__ubuntu_noble_amd64, because we've moved to Resolute. So I assume the job name won't be the same

Good point, I've removed that for now.

[cottsay]

@ros-pull-request-builder retest this please

[christophebedard]

Alright. We only have an Lpr job and no Rpr job, but I think that's OK. This fix concerns both Rolling and Lyrical