API Alignment

[DariusIMP]

This PR extensively updates the Zenoh Java API.

Api modifications:

Removing all builder patterns and resolvables

We noticed this kind of API was causing confusions among Java users:

publisher.put(payload).attachment(attachment).res();

For 2 reasons:

• the imperativeness of statements such as "put" doesn't make you think it's in fact returning a builder
• the .res() call was often forgotten

It was decided to go for an approach similar to the C++'s bindings with Option objects, for instance:

PublisherOptions options = new PublisherOptions();
options.setEncoding(Encoding.ZENOH_STRING);
options.setReliability(Reliability.RELIABLE);
Publisher publisher = session.declarePublisher(keyExpr, config);

New features introduced:

• Scouting
• Liveliness
• ZBytes (replacing Value)
• SessionInfo

Documentation:

All the documentation was updated with examples following the new API.

Misc:

Logger refactoring

Logs can now be achieved by running for instance:

RUST_LOG=debug gradle ZGet

similar to other Zenoh bindings.

Packages reordering

• Aligning the sorting of classes and packages with the other bindings

Adding new examples

• Added examples: Zping, ZPong, ZScout

• Also providing argument handling to them with 'picocli'.

Encoding updates

Internal:

• Porting tests from kotlin to java
• Adoption of the "@JvmOverload" tag

Missing items

ZBytes serialization and deserialization utilities, to be added in a followup PR.

[github-actions]

PR missing one of the required labels: {'bug', 'internal', 'documentation', 'breaking-change', 'new feature', 'enhancement', 'dependencies'}

[milyin]

Looks good, but some options structures doesn't implement setters/getters.

[DariusIMP]

I just changed a couple of things:

• Added the GetOptions instance on the ZGet example
• Refactored the Options classes regarding the QoS config