e2e tests: Containerfile presence

[slimreaper35]

Maintainers will complete the following section

• [ ] Commit messages are descriptive enough
• [ ] Code coverage from testing does not decrease and new code is covered
• [ ] Docs updated (if applicable)
• [ ] Docs links in the code are still valid (if docs were updated)

Note: if the contribution is external (not from an organization member), the CI pipeline will not run automatically. After verifying that the CI is safe to run:

• approve GitHub Actions workflows by clicking a button
• approve the Red Hat Trusted App Pipeline container build by commenting /ok-to-test (as is the standard for Pipelines as Code)

[slimreaper35]

Are you okay with this change? In the future, when creating new e2e tests, part of the repo can / should be Containerfile, too.

I think it will make life easier when testing locally. Also, I suppose users have their Containerfile in the same repo when using cachi2.