Make SCM determine the schema version of new containers

Currently when SCM instructs a pipeline of datanodes to create a container, it does not specify the schema version (disk layout) of that container. Some layout features like HDDS-3630 may introduce new container schemas or other features specific to new containers. If we want to finalize these features without closing all containers or blocking new container creation, SCM must instruct all datanodes in a pipeline to create containers in accordance with the lowest metadata layout version present on any datanode. This ensures that all replicas of the same container are using the same schema version.