Add support for network visualiser when connected to shared instance

[markqvist]

This PR adds support for parent/child interface visualization when connected to a shared RNS instance, and removes dependency on manually getting certain interface-specific characteristics such as hash and name, since these were added natively in RNS 42319a092db0d593e35f07478d1eece907f3bb88.

Also fixes a bug where the network visualizer would fail if a probe responder was active on the transport node.

[markqvist]

Tested on one of my well-connected testnet hubs with ~120 interfaces. Much spring, but works nicely!

[liamcottle]

Holy moly! That's a fair few interfaces!

Thanks for the PR and for adding those extra infos natively :)

I'll get this merged in once RNS has a release available to pull in.

[markqvist]

Thanks for the merge! It would be quite nice if you can also add custom display names to the network visualiser, so that if a custom name is set on a conversation, it will use that in the visualiser too. I tried messing around with it a bit today, but I am completely unfamiliar with Vue, and figured I'd likely just break something, or implement it wrong, so I'd rather leave it to you :) Just a humble request, but man would it be nice :)

[liamcottle]

Done :) Added in 000b515 and 1c1d820

[markqvist]

AWESOME!

[faragher]

Question: Does this generalize out to being able to look at "parent_interface_name/hash" on any shared Reticulum instance for identifying which interface an announce came in on?