Registering previously registered holoport creates stale entries in ZT Central

[peeech]

Whenever user is registering holoport with holochain_agent_id that has already been registered a new entry is created in ZT Central registry.

ZT Central is using address field as a unique key, but many services downstream use name field (which is populated with holochain_agent_id) as a unique key. Because process mentioned above creates multiple entries with the same name value the structure of database from the perspective of downstream services is corrupted.

So in the name of brotherhood with downstream consumers I am suggesting deleting all the old entries where name == holochain_agent_id while creating a new entry.

This would require making 1 more call after this line of a server code.

[alastairong]

This is more complex as we want to make sure we don't lose any data from their past life e.g. uptime history.

So in theory yes, in practice let's think through this carefully.

[alastairong]

Have checked matching-engine code and this is fine.