align clone methods: coordination task

[milyin]

Describe the release item

after the discussion on eclipse-zenoh/zenoh-c#549 issue the following approach for clone implementation was proposed

• Rust: objects which implements undeclare operation should not be clonable. E.g. Publisher should not be clonable, because if one copy is undeclared, another one ceases to work too
  • remove clone from Publisher #1371
    ....
• zenoh-c, zenoh-pico and zenoh-cpp should either follow the behavior of Rust API or be even more restrictive in cloning (discussable)
  • zenoh-c add hello and string_array clones zenoh-c#678
  • zenoh-pico Remove clone for types which do not involve copying zenoh-pico#645
  • zenoh-cpp api alignment zenoh-cpp#211

zenoh-c and zenoh-pico should pass mutable z_loaned_xxx_t* parameter to callback and should provide z_take operation for taking value from such mutable loaned reference. This allows user to either take ownership of passed value or keep it for caller. Now this is achieved by cloning const z_loaned_xxx_t* object.

This task can be split into 2 parts, it's enough to implement only first one for 1.0.0 release

• pass mutable z_loaned_xxx_t* parameter to callbacks
  • zenoh-c made closure param mutable zenoh-c#677
  • zenoh-pico Make callback closures provide mutable loaned structs zenoh-pico#647 Remove const from closure params zenoh-pico#653
  • zenoh-cpp Align with zenoh-c/pico zenoh-cpp#213
• provide z_take operation for taking value from mutable loaned reference (API extension, can be done in 1.1)
  • zenoh-c take operation accepts mutable loaned reference for types which supports it zenoh-c#718
  • zenoh-pico
  • zenoh-cpp

[milyin]

Closing the issue, the "take_from_mutable" eclipse-zenoh/zenoh-c#718 remains open, no need to covet it here anymore