Map to non-compliant topic structures

[bluemonk3y]

Many users with an existing installation want to use specmesh on non-structured/non-compliant topics

Resolution

1. ACL/Permissions - support permission configuration via channel tags: _public, _private, _protected
2. Root Id - specmesh uses a root id as the ACL/Domain owner - this doubles as the service id (no change)
3. Define absolute paths on owned topics. See below.

Normally topics are appended to the id. i.e. domain-owner + permission + topic. In this case, the topic:

1. doesn't start with _public/_private/_protected, imported/requested topic are of the form:
2. a remote topic like: acme.simple_range.transport._public.tube. id: acme.simple_range'

Resolution:

1. Require topics to include the same id on the prefix. i.e. domain: acme.domain-id is located at the id and also used on the topic prefix. The only difference here is there is no permission prefix _public etc. it requires a permission tag - see Resolution item 1. above

This approach will grant permission ACLs/metrics because the topic prefixing with the domain id is supported. Installations without a domain id - must be 'imported'

Therefore we can use

domain-id.topic-name
as opposed to the expected
domain-id.{permission}.topic-name

In short, the resolution is to:

• support moving the permission to the tag on the channel
• document it

Required for #184