Improving Micro-ROS

Since the last devlog, a bunch of stuff has happened:

1. I am now a maintainer of Micro-ROS! The story is that I noticed the current maintainers were a bit inactive, so I emailed them to ask if they could make me a maintainer so I could get PRs merged faster and close stale issues. Looking at my previous open-source contribution experience, they responded with a yes and made me a maintainer.
2. I got my PRs reviewed by other maintainers and got them merged!

I have finally started working on Zenoh support in Micro-ROS, the thing I started this project for. rmw_zenoh_pico had some patches for zenoh-pico to make it work better with Micro-ROS (rmw_zenoh_pico currently only has support for running Zenoh with Micro-ROS on Linux, not on microcontrollers). They didn’t work for the latest zenoh-pico versions and needed some cleanup. I did the necessary changes, and now zenoh-pico is building just fine with colcon for ESP-IDF.
rmw_zenoh_pico is currently failing as it was originally made to work on ROS 2 Jazzy, not Rolling. I will fix that in the next devlog.

I made many improvements to the GitHub Actions CI and README.md of the micro_ros_espidf_component to make it easier for me to test my changes. PR: https://github.com/micro-ROS/micro_ros_espidf_component/pull/324

I then worked on getting the component to properly work with ESP-IDF v5.5. I took most of my changes from another PR and retargeted them to rolling. My PR: https://github.com/micro-ROS/micro_ros_espidf_component/pull/325

I got the ROS 2 Rolling builds fixed and made a PR.
Look at the screenshot below or the PR for more details.

I have started by trying to build and run the micro_ros_espidf_component default examples using rmw_microxrcedds.
I first created a flake.nix for the project (something which I do for all my projects). I used nixpkgs-esp-dev for this.
When attempting to build the first example in ROS2 Rolling, I encountered an error. Turns out that right now Micro-ROS is not working for rolling due to a new package added to rcl_logging. I decided to address this issue as well.