tedge has inconsistent default topics for aws and az

[reubenmiller]

Describe the bug

The tedge config list topics shows that the default topics used by the mappers have different defaults (which is unexpected as each mapper should send the same data to the cloud).

$ tedge config list topics

c8y.topics=["te/+/+/+/+", "te/+/+/+/+/twin/+", "te/+/+/+/+/m/+", "te/+/+/+/+/e/+", "te/+/+/+/+/a/+", "te/+/+/+/+/status/health"]
az.topics=["te/+/+/+/+/m/+", "te/+/+/+/+/e/+", "te/+/+/+/+/a/+", "te/+/+/+/+/status/health"]
aws.topics=["te/+/+/+/+/m/+", "te/+/+/+/+/e/+", "te/+/+/+/+/a/+", "te/+/+/+/+/status/health"]

The az.topics and aws.topics are missing the following topics:

• te/+/+/+/+
• te/+/+/+/+/twin/+

To Reproduce

Check the default settings by running:

tedge config list topics

Expected behavior

• The default c8y, aws and az mapper topics should be the same.
• The root prefix should also be respected when the tedge-mapper subscribes to the local thin-edge.io topics

Screenshots

Environment (please complete the following information):

• OS [incl. version]: any
• Hardware [incl. revision] any
• System-Architecture [e.g. result of "uname -a"]: any
• thin-edge.io version [e.g. 0.1.0]: 1.4.2

Additional context