Fix lingering containerd config issues

[tjkirch]

commit b03bb3c3f4b5a48092efcfd3253587e38f5db10b
Author: Tom Kirchner <tjk@amazon.com>
Date:   Wed Dec 18 13:27:03 2019 -0800

    Disable CRI plugin in aws-dev image's containerd config
    
    We already removed all of the CRI config in the dev image, but forgot to
    disable the plugin.

commit b9f90233b14f0ec3f6b2c2f66bfbd4b36a2d4349
Author: Tom Kirchner <tjk@amazon.com>
Date:   Wed Dec 18 13:32:29 2019 -0800

    Remove /etc/containerd/config.toml from containerd tmpfiles config
    
    f9784cb20505 removed config.toml from factorydir but we didn't remove it from
    tmpfiles, which led to a "No such file" error at startup.

---

Testing done:

Made aws-k8s AMI, Kubernetes still connected and a pod worked, admin/sheltie worked. Made aws-dev AMI, admin/sheltie worked, ran a Docker container OK.

No longer see the above "No such file" error on startup.