Add support for Zenoh transport

[gonzalocasas]

What type of change is this?

• Bug fix in a backwards-compatible manner.
• New feature in a backwards-compatible manner.
• Breaking change: bug fix or new feature that involve incompatible API changes.
• Other (e.g. doc update, configuration, etc)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I added a line to the CHANGELOG.md file in the Unreleased section under the most fitting heading (e.g. Added, Changed, Removed).
• I ran all tests on my computer and it's all green (i.e. invoke test).
• I ran lint on my computer and there are no errors (i.e. invoke lint).
• I added new functions/classes and made them available on a second-level import, e.g. compas.datastructures.Mesh.
• I have added tests that prove my fix is effective or that my feature works.
• I have added necessary documentation (if appropriate)

[gonzalocasas]

@chenkasirer and by extension, ping here as well ;)

[chenkasirer]

LGTM!

[chenkasirer]

judging by the name, it sounds like this method has side-effects but it's just putting together an identifier? am I missing anything?

[gonzalocasas]

This is due to the API being modeled after ROS' api that requires advertising before publishing. Perhaps we should make a breaking-change at some point and move away from ROS terminology on the public API level