Fix for #6531 "broke" some mesh-gateway configuration features

#6531 introduced more tagged addresses that are IP protocol specific. During registration if the `lan` or `wan` addresses are set we will also auto-configured the `lan_` and `wan_` tagged addresses. This usually results in duplicate addresses within the tagged_addresses map.

The mesh-gateway when configured to bind to the tagged addresses will attempt to create 1 listener per tagged address which will result in errors due to not being able to bind to the ip/port multiple times.

We should dedup those addresses somehow and create 1 listener per distinct IP address. The complexity here will mostly be around which name to use since the address is bound to multiple names.