Fix Local modifications exist in repository

Depending on the state of upstream repositories, it's possible the
kubernetes repo could change between the ``setup`` and ``run`` phase.
Alternatively, something during ``setup`` itself could mangle the repo.

Add an option to force clone the kubernetes repo.  This gives support
for testing on multiple CRI-O branches, realizing some benefit from
caching, yet also allows hauling in brand-new-kubernetes for the e2e
tests.

Signed-off-by: Chris Evich <cevich@redhat.com>

contrib/test/integration/e2e.yml

@@ -1,8 +1,5 @@
 ---
 
-- name: clone build and install kubernetes
-  include: "build/kubernetes.yml"
-
 - name: enable and start CRI-O
   systemd:
     name: crio