Running the e2e tests takes a while to validate inputs

[rhmdnd]

In the process of running the e2e tests locally, the tests appear to hang before failing because I didn't specify the profile I wanted to test.

After digging through the code, the test wasn't actually hanging, it was just taking a long time for the tests to clone the ComplianceAsCode/content repository. After it finally cloned the repository, it failed because I didn't supply the right inputs.

We might improve this experience by validating the user has supplied the necessary inputs before starting to setup the tests. This allows us to fail early, shortening the feedback loop for the user.

[rhmdnd]

I'm debugging some e2e failures in the ComplianceAsCode/content CI and noticed this. I can push a patch as soon, but I didn't want to lose this in the mix.