use containerd for the container workload in kubeup and kubemark

[sonyafenge]

What happened:
kubeup and kubemark still uses default runtime, in this case, the dockershim. This might be OK if we want a true apple to apple comparison with the community version of Kubelet. But in reality, those test results for Arktos are not much meaningful since Arktos, as a shared multi-tenant platform, cannot use the docker as runtime at all.

Suggest we start using containerd as the runtime as soon as possible so we can have a better feeling about the true Arktos perf or scalability quality level prior to our first release.

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Arktos version (use kubectl version):
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Network plugin and version (if this is a network-related bug):
• Others: