[Integration] Podman preset tests

[jsliacan]

Relates to: Issue #2920

This PR sets up integration tests to work with podman preset on all 3 platforms. The test itself is barely populated, but this will be remedied when we pull in some tests from the podman e2e suite.

[anjannath]

@jsliacan Looking at the job logs, the CI failures seems to be because it can't find the correct podman bundle and trying to run setup with the libvirt bundle.

level=info msg="Getting bundle for the CRC executable"
[387](https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/code-ready_crc/3081/pull-ci-code-ready-crc-main-integration-crc/1514175911950290944#1:build-log.txt%3A387)
        level=debug msg="Ensuring directory /home/packer/.crc/cache exists"
[388](https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/code-ready_crc/3081/pull-ci-code-ready-crc-main-integration-crc/1514175911950290944#1:build-log.txt%3A388)
        crc_libvirt_4.10.6_amd64.crcbundle is not supported by this crc executable, please use crc_podman_libvirt_3.4.4_amd64.crcbundle
[389](https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/code-ready_crc/3081/pull-ci-code-ready-crc-main-integration-crc/1514175911950290944#1:build-log.txt%3A389)

Currently we can't set the "bundle" in the testing code right? its configurable using an env variable, which is fixed for the whole test run, but now since we have tests that expects two (and more..) kinds of bundles, maybe we should make this configurable from the testing code?

[jsliacan]

@anjannath yes, you're right for one PR check, both bundles will be needed. I'll have a look and suggest some changes. I'll make it a separate commit. Thanks!

[openshift-ci[bot]]

@jsliacan: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[anjannath]

@jsliacan are these tests supposed to exists along and separate from the upstream tests from podman as i think the upstream tests will be stand alone and we won't pull in actual test code to our repo?

[anjannath]

/test e2e-crc

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anjannath

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• ~~OWNERS~~ [anjannath]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[anjannath]

@jsliacan are these tests supposed to exists along and separate from the upstream tests from podman as i think the upstream tests will be stand alone and we won't pull in actual test code to our repo?

got reply in slack that upstream podman tests are going to be stand alone or an extension of this, is not yet decided, merging this and we can add necessary changes to extend this as needed