Remove volumesfrom from the config

This does not have any backwards incompatible changes in it.  There is no need for migration of existing containers. 

After a container is started the volumes and volumes-from configuration is loaded from the config and used to populate the volumes specific to the container. 

As for images with this field populated, it will be ignored and not cause any issues.  Old versions will be fine with new images created.  

Fixes #5062