Remove atomic patch & sed for flags, add support for idf 5.3, 5.4 (Humble)

[Narukara]

Since newer versions of ESP-IDF provide complete atomic operations, we can disable the 64-bit atomic extension in micro-ROS/rcutils and remove the complex patch_atomic mechanism. See #251.

Remove unnecessary sed commands in libmicroros.mk to ensure compatibility with ESP-IDF 5.5.4. See #327.

Added support for ESP-IDF 5.3 and 5.4 (already verified through CI checks in my fork).

[Narukara]

About atomic operations:

All the required atomic operations — which are also the ones provided by micro-ROS/rcutils (see this and this) — are the following four:

• __atomic_load_8
• __atomic_store_8
• __atomic_exchange_8
• __atomic_fetch_add_8

All of these are fully provided in newer versions of ESP-IDF.

ESP-IDF version	source code
4.4	https://github.com/espressif/esp-idf/blob/a9d0f22193acdf47a5a4db36832ae7068818962b/components/newlib/stdatomic.c#L424-L490
5.2	https://github.com/espressif/esp-idf/blob/bc2a328c969a2c9d5948f7e6f862a526b6c162a4/components/newlib/stdatomic.c#L451-L519
5.3	https://github.com/espressif/esp-idf/blob/78a04b369d2d54bc640b050e45ad4eca76f2b71a/components/newlib/stdatomic.c#L77
5.4	https://github.com/espressif/esp-idf/blob/9c4bbcdacee1186201f54954f74f9aed78cba2ca/components/newlib/stdatomic.c#L85
5.5	https://github.com/espressif/esp-idf/blob/e46782886f6ddb007e1a46f32d3725ac1135f0ba/components/newlib/src/stdatomic.c#L85

[Narukara]

@Amronos Thank you for accepting my proposal!

I'd like to confirm what exactly the criteria are for "tested" in the README. Does it require running each example program on actual hardware?

Also, what's your plan — are you thinking of adding support to the rolling branch first and then backporting to other branches? I'm wondering if maybe this PR isn't suitable for merging.

[Amronos]

I'd like to confirm what exactly the criteria are for "tested" in the README.

Since I am not a maintainer of this repo, I am not too sure.
But I personally feel that it should be fine to test it one one or two different pieces of hardware and make sure everything builds fine in CI.
If any bugs occur, they can be fixed once reported.

Also, what's your plan

The general pattern I have seen in other repositories is to merge everything first to rolling and then perform backports through tools like mergify for consistency between branches.
That doesn't seem to be the case here as different PRs adding support for esp-idf v5.5 were directly merged to jazzy and humble.

Another thing:
The maintainers of this repo do seem a bit inactive; I am considering making a post on ros discourse or zulip to ask for maintenance rights to this repo so that we can get PRs merged faster. Would you like to join?

[Narukara]

Another thing: The maintainers of this repo do seem a bit inactive; I am considering making a post on ros discourse or zulip to ask for maintenance rights to this repo so that we can get PRs merged faster. Would you like to join?

I'm glad to join. But I think we should check with the maintainers first... @pablogs9 @EugenioCollado

Actually, I'm planning to adapt this library for ESP-IDF 6.0 and above. Also, to add this library to the ESP Component Registry.

[Amronos]

Agreed with everything. I will make a post in about a week if there is no response.