Move reliability parameter from subscriber to publisher

[Mallets]

Describe the release item

At the moment reliability parameter is set at subscriber declaration.
However, handling the proper setting of reliability value of any publication requires quite a complex matching strategy that may have a negative impact on performance. Moreover, propagating the subscription declaration requires a complex update/merging strategy upon interleaved declare/undeclare.

Therefore, it would be recommended to move the reliability parameter from the subscriber to the publisher.
Current:

let sub = session.declare_subscriber("foo").reliability(Reliability::Reliable).await.unwrap();
let pub = session.declare_publisher("foo").await.unwrap();
session.put("foo").await.unwrap();

New:

let sub = session.declare_subscriber("foo").await.unwrap();
let pub = session.declare_publisher("foo").reliability(Reliability::Reliable).await.unwrap();
session.put("foo").reliability(Reliability::Reliable).await.unwrap();

In addition, the default value of Reliability should be set to Reliable and not BestEffort as it is in the current version.

• Rust Publisher reliability #1305 Remove subscriber reliability option #1353
• C Move reliability to publisher zenoh-c#652 move reliability to publisher zenoh-c#653
• C++ move reliability to publisher zenoh-cpp#203
• Pico Move reliability parameter from subscriber to publisher zenoh-pico#614 Switch reliability from subscriber to publisher. zenoh-pico#630
• Python feat!: remove reliability from subscriber zenoh-python#308 feat: add reliability to publisher zenoh-python#311
• Kotlin Moving reliability config param from subscriber to the publisher, and to session put and delete zenoh-kotlin#199
• TS https://github.com/ZettaScaleLabs/zenoh-ts/issues/3

[wyfo]

For Python: eclipse-zenoh/zenoh-python#308
@Mallets As the reliability parameter is unstable for declare_publisher, and as there is even no reliability getter for Publisher, should it be added to Python now?

[DariusIMP]

For Kotlin: eclipse-zenoh/zenoh-kotlin#199

[Mallets]

For Python: eclipse-zenoh/zenoh-python#308 @Mallets As the reliability parameter is unstable for declare_publisher, and as there is even no reliability getter for Publisher, should it be added to Python now?

Yes. If the reliability getter is missing in Rust, we can add it.

EDIT: Added in #1393

[milyin]

Closing the issue, the TS issue remains, but no need to track it here