RadiatorDB collection destroy completed

Logged when an operator destroys a RadiatorDB collection on every configured node that is not deprovisioned. Writes were stopped and replication between the nodes caught up before the collection storage was dropped, and each node also removed the collection from its setup evidence. The collection field names the destroyed collection, and destroyed_nodes lists the nodes that stored it. For a storage conflict, kept_nodes lists the nodes that store the collection with the configured storage and keep it.

No action is required when the collection is no longer configured. If the collection is still configured, the next restart or configuration reload recreates it as an empty collection with the configured storage; remove its collection block from the RadiatorDB backend if it should not be recreated.