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.