Possible to define duplicate addresses (using router pattern matching syntax)

[k-wall]

Describe the bug

https://qpid.apache.org/releases/qpid-dispatch-1.10.0/user-guide/index.html#router-address-pattern-matching

The router considers the following addresses as equal:

• foo/bar
• foo.bar
• /foo/bar
• .foo.bar

EnMasse doesn't know about about the special meaning of the separator characters so will try to treat them as distinct address and try to create them all. The router will reject the dups and report address prefix conflicts with an existing entity internally (admin). The duplicates will stay in the unready state.

To Reproduce Steps to reproduce the behavior:

1. Create two or more anycast addresses with the names given above.
2. Observe that the second address remains in the unready state forever.

Expected behavior

We need to decide if the router's address pattern should be expose to users of EnMasse. If so, how should this behave in the brokered space.