Inconsistent behavior when multiple dispatch running in the same network

[DGonzalezVillal]

Saw behavior that when there are 2 (assuming can be reproducible with more) dispatch up in the same network, beacon fails to boot to the one that is assigned to it. Early hypothesis is that the browsing feature in beacon isn't cycling through discovered nodes after failures.

[markg-github]

It looks like this is due to Avahi name collisions. Avahi itself includes logic to modify these names to avoid collisions, but, apparently, with the way that we're using Avahi, we don't get this for free (and we don't do what's necessary to get it at all). I'll be opening a PR soon that adds two command line options, both of which allowing a suffix to be added to the name, either random or as specified on the command line.