Add CRI-O to TestStartStop

[tstromberg]

This helps us from accidentally breaking CRI-O support in future PR's.

This PR does fall short of running all tests in CRI-O, but that will have to wait for the Prow migration where we can run more advanced test matrixes.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tstromberg

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [tstromberg]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tstromberg]

@minikube-bot OK to test

[afbjorklund]

LGTM, possibly add --network-plugin=cni ?

[afbjorklund]

The documentation even says:

$ minikube start \
    --network-plugin=cni \
    --enable-default-cni \
    --container-runtime=cri-o

https://github.com/kubernetes/minikube/blob/master/docs/alternative_runtimes.md#using-cri-o

So should probably use the exact same parameters, when testing ?

i.e. --enable-default-cni too

[tstromberg]

The documentation even says:

$ minikube start \
    --network-plugin=cni \
    --enable-default-cni \
    --container-runtime=cri-o

https://github.com/kubernetes/minikube/blob/master/docs/alternative_runtimes.md#using-cri-o

So should probably use the exact same parameters, when testing ?

i.e. --enable-default-cni too

I shouldn't have to look at documentation to select a container runtime - our defaults are terrible. Opened #3567 to address. Updated PR.