automation: use a constant ginkgo seed
automation: use a constant ginkgo seed

Our tests are too fragile. Our CI fails to often and people do not take
failures seriously enough, as following execution may pass.

I suspect that some of the problem is due to the randomization of tests.
In this patch I suggest to stabilize the test order, so we have more
predictability. Once all flakiness is removed, we should try few other
constant seeds. When we are certain that none of them trigger flakiness
we can consider reintroducing random seed, to increase our coverage.

Signed-off-by: Dan Kenigsberg <184831158ae7531bcabc22617ed51e8717c81e93@redhat.com>

stu-gott/kubevirt,kubevirt/kubevirt,kubevirt/kubevirt,kubevirt/kubevirt,stu-gott/kubevirt,davidvossel/kubevirt,kubevirt/kubevirt,davidvossel/kubevirt,davidvossel/kubevirt,stu-gott/kubevirt,davidvossel/kubevirt,stu-gott/kubevirt