e2e: Support CRC "cloud provider"

[kaovilai]

Is your feature request related to a problem? Please describe.

While testing openshift/velero#353 (comment) with https://github.com/crc-org/crc, following is observed.

~/git/velero oadp_e2e_velero
❯ make -f Makefile.prow test-e2e 
Cloning oadp-operator
rm -rf /tmp/oadp-operator
git clone --depth 1 --single-branch --branch master https://github.com/openshift/oadp-operator.git /tmp/oadp-operator
Cloning into '/tmp/oadp-operator'...
remote: Enumerating objects: 487, done.
remote: Counting objects: 100% (487/487), done.
remote: Compressing objects: 100% (395/395), done.
remote: Total 487 (delta 105), reused 316 (delta 76), pack-reused 0 (from 0)
Receiving objects: 100% (487/487), 10.46 MiB | 6.88 MiB/s, done.
Resolving deltas: 100% (105/105), done.
Running oadp-operator e2e tests
pushd /tmp/oadp-operator && export VELERO_IMAGE=quay.io/konveyor/velero:latest && make test-e2e && popd
/tmp/oadp-operator ~/git/velero
bash: /tmp/oadp-operator/bin/setup-envtest: No such file or directory
$CLUSTER_TYPE is [none]
cat: /var/run/oadp-credentials/new-velero-bucket-name: No such file or directory
mkdir -p /tmp/test-settings
TMP_DIR=/tmp/test-settings \
        OPENSHIFT_CI="true" \
        PROVIDER="none" \
        AZURE_RESOURCE_FILE="/var/run/secrets/ci.openshift.io/multi-stage/metadata.json" \
        CI_JSON_CRED_FILE="/Users/drajds/.aws/osServicePrincipal.json" \
        OADP_JSON_CRED_FILE="/var/run/oadp-credentials/azure-credentials" \
        OADP_CRED_FILE="/var/run/oadp-credentials/new-aws-credentials" \
        BUCKET="" \
        TARGET_CI_CRED_FILE="/Users/drajds/.aws/.awscred" \
        VSL_REGION="" \
        BSL_REGION="us-east-1" \
        BSL_AWS_PROFILE="default" \
        /bin/bash "tests/e2e/scripts/none_settings.sh"
/bin/bash: tests/e2e/scripts/none_settings.sh: No such file or directory
make[1]: *** [test-e2e-setup] Error 127
make: *** [test-e2e] Error 2

~/git/velero oadp_e2e_velero
❯ 

Describe the solution you'd like

Describe alternatives you've considered

Additional context

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kaovilai]

/lifecycle frozen