RadiatorDB collection created

Logged when RadiatorDB setup creates a newly configured collection on every configured node. Setup serves a new collection only after it exists on every node, so it waits until every configured node is set up and serving, except nodes that join the cluster, and then creates the collection on all of them at once. The collection field names the collection and created_nodes lists the nodes where it was created. When adopted_nodes is present, it lists the nodes that already stored the collection with the configured storage, for example after another Radiator Server process created it first or after an earlier attempt committed on some nodes only. Adopted nodes keep the documents they store. When evidence_failures is present, those nodes could not record the collection in their setup records, and the field gives each error. The collection is served, but if no node recorded it, setup serves it after a restart only once every configured node is set up again.

If evidence_failures is present, check the reported error and the PostgreSQL server of each listed node. Otherwise no action is needed.