[Bug] Forward Discovery not transferring some qos policies

[ben-parkin]

Describe the bug

When using zenoh with forward discovery to bridge a domain gap between two cyclone applications, its seen that the copy of a reader or writer does not carry some QoS policies over to its "clone".

For example, a writer on domain 1 (d1) has a:
durability = transient_local
reliability = best_effort
liveliness.lease_duration = 30 seconds
history.depth = 100

when a second zenoh and reader is ran on domain 2 (d2) the copied or "cloned" writer made by the zenoh bridge on d2 has the following properties:
durability = transient_local (it copied! 🥳)
reliability = reliable (default 😢)
liveliness.lease_duration = 30 seconds (it copied! 🥳)
history.depth = 1 (default 😢)

(this is identified using cyclone-insight tool)

Is this a known behaviour with the zenoh-bridge or with dds that these properties cannot be translated to other dds entities? Further more is the purpose of the forward discovery to create a 1:1 copy of the writer/reader that is using the zenoh in this way or is it known that some properties will always take their default setting (based on either cyclone or OMG standards).

To reproduce

1. Create publisher on domain 1
2. Change qos durability setting to "best effort"
3. Create base subscriber on domain 2
4. Run zenoh bridges on both domain 1 and 2 with -f flag
5. Observe settings on zenoh created writer on domain 2

System info

• Zenoh version / Commit: bfb9e93