WiredTiger currently supports the publish API and uses the metadata updates queue for schema operations only for layered tables and for layered objects that are not tables.

As we currently don't plan to support the publish API for non-layered objects, this might be an overkill, but it would give us a few benefits. For example, this would allow us to enforce that applying the UPDATE operation in __disagg_shared_metadata_op does not create new metadata entries.