Upload to the ESP component registry

[Narukara]

See #369

Publish Kilted as version 25.0.0.

[mergify]

@Narukara, all pull requests must be targeted towards the rolling development branch.
Once merged into rolling, it is possible to backport to kilted, but it must be in rolling
to have these changes reflected in new distributions.

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[Amronos]

This approach looks good to me. Before merging this PR, do we need a component with the name micro-ros/micro_ros_espidf_component created in the ESP component registry, or has that already been done? cc: @EugenioCollado

[Narukara]

do we need a component with the name micro-ros/micro_ros_espidf_component created in the ESP component registry

I had the same concern. The MR CI dry run passed, but it appears that upload-components-ci-action does not validate permissions in dry-run mode. We should still confirm this with him.

[Narukara]

Another minor issue is that the banner in the README does not render correctly in the registry. It may need to use a URL such as https://raw.githubusercontent.com/.... Also, switching images based on the light or dark theme is somewhat difficult in the registry.

[EugenioCollado]

LGTM

[Narukara]

Before merging this PR, do we need a component with the name micro-ros/micro_ros_espidf_component created in the ESP component registry

I tested this on https://components-staging.espressif.com/, and it turns out that a component does not need to be created manually in advance before it can be uploaded. It works as long as Trusted Uploaders are configured at the namespace level.

[Narukara]

Anyway, I merged the PR, and the CI is now failing with an authentication error. This suggests that the previous Trusted Uploaders configuration was set at the component level, and the component name is not the one we want.

At this point, we need to do one of the following:

• Configure Trusted Uploaders at the namespace level to allow uploads from this repository; or
• Create the micro_ros_espidf_component component under the micro-ros namespace first, and then configure Trusted Uploaders for that component. I would recommend this option.

@EugenioCollado, could you help set this up? I assume the setup would look something like this:

Once the configuration is in place, rerunning the upload job should be enough.

[EugenioCollado]

I have done the steps for the second option and rerun the workflow and it is green now: https://github.com/micro-ROS/micro_ros_espidf_component/actions/runs/31372302915/job/93424230482