multi-tenancy support

If the same Falcon topology is run twice on the same machine, ZFS and data link names will collide. This is extremely unfortunate for shared lab environments.

A workaround is that users can give topologies unique names. There are a few ways to go about sorting this out.

1. Add a random string or a counter of some kind to topology names.

If we choose the random string, it would need to be somewhat short, as we can easily bump up against OS limits for link names. If we choose the counter, system-wide coordination would be needed.

2. Use random IDs for link names and ZFS names.

If we do this, features would need to be built into the Falcon CLI utilities to map the random names to topology-relevant names to aid in debugging and general observability.

Start by reviewing the Falcon CLI utilities and the topology, data-link, and ZFS naming paths described in the issue. Compare unique topology names with random link and ZFS names, including the stated OS link-name limits and coordination concerns. Done means two Falcon topologies can run on one machine without name collisions; if random IDs are chosen, the CLI must map them to topology-relevant names for debugging and observability.