Handle metadata collection id in config documents

[planetf1]

The operator uses existing configuration documents. Often these may have been created through the server author UI and so would not contain a metadata collection id

On startup, an egeria server will create a metadata collection id in the config, yet in our current operator design, that config document is effectively R/O. This will mean that on next startup of the server it will be out of sync with the actual metadata repository, and (should) fail to start

If the config document already contains an id, then this will work fine AS LONG AS it matches the metadata repository (likely to be crux or similar)

Need to consider how to handle these situations through doc/code