Decide what to do about iceoryx2 and Zenoh

Validated in a recent codebase, iceoryx2 and Zenoh work remarkably well out of the box, even with minimal configuration, for the use cases airo-ipc proposes (SHM IPC and multi-host IPC). They are also more feature rich.

The main benefit airo-ipc still has, is a unified interface that makes it easy to use, though that is not entirely the case because SHM data types are different from DDS data types.

iceoryx2 has a work-in-progress Zenoh tunnel which allows to use just one interface (iceoryx2 then uses Zenoh under the hood to transport messages across hosts), but it's still subject to change.

The reasonable level of maturity of these two libraries forces us to reevaluate whether airo-ipc needs to exist. We knew from the start that this day would come, and decided to develop airo-ipc for time-sensitive use cases.

I see three options:

1. Leave airo-ipc as it is. It's fairly easy to use, and works well for most use cases. Bugs will probably continue to arise.
2. Release the current version as "1.0.0" and release a new version "2.0.0" which provides a unified interface that uses iceoryx2 and Zenoh under the hood. Only relevant until the iceoryx2's Zenoh tunnel matures.
3. Deprecate airo-ipc. Tell users to move to iceoryx2 and/or Zenoh. Requires that they learn two new APIs.

To be continued...