e2e: Perform crc setup after moving the clock 3 months ahead

The cert renewal e2e test moves the clock 3 months ahead in order to
make sure certificate renewal is working as expected.

However, `crc setup` is run during the time travel. Since `crc setup`
can try to create TLS connections to public servers (when using 'yum'
for example), this could fail unexpectedly as the certificates used by
these public servers may not be valid for 3 more months.

This commit moves crc setup before the date change to avoid such issues.

After the reordering, a short wait is needed for libvirt to become
available again, as `date -s "5 minutes" && virsh hostname` is failing
for a few seconds after the time jump.

Author: cfergeau

test/e2e/features/cert_rotation.feature

@@ -5,12 +5,15 @@ Feature: Certificate rotation test
     certificate rotation to happen successfully and to be able to deploy
     an app and check its accessibility.
 
+    Scenario: Setup CRC
+        Given executing "crc setup" succeeds
+
     Scenario: Set clock to 3 months ahead on the host
         Given executing "sudo timedatectl set-ntp off" succeeds
         Then executing "sudo date -s '3 month'" succeeds
+        And with up to "10" retries with wait period of "1s" command "virsh --readonly -c qemu:///system capabilities" output matches "^<capabilities>"
 
     Scenario: Start CRC
-        Given executing "crc setup" succeeds
         When starting CRC with default bundle along with stopped network time synchronization succeeds
         Then stdout should contain "Started the OpenShift cluster"
         And executing "eval $(crc oc-env)" succeeds