chore: split e2e tests into 2 packages, vm and container

[davidhsingyuchen]

Summary

PR fixes #142 (comment) by splitting container tests and vm tests into different binaries (i.e., different packages) to make sure that the former is run before the latter.

The package-level comment of the e2e package provides more details, so reading it first may make reviewing this PR easier.

License Acceptance

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[pendo324]

The split makes a lot of sense after reading the package level comments, you did a great job citing the Ginkgo docs. But I wonder if vm is the best name for the package, since it also contains test for config and the version command. Does something like container and app make sense? Or maybe container and cli or common and cli? Definitely open to discussion here

[davidhsingyuchen]

@pendo324

The split makes a lot of sense after reading the package level comments, you did a great job citing the Ginkgo docs.

Thanks. Updated the PR description to recommend reviewers to read the package-level comments first.

But I wonder if vm is the best name for the package, since it also contains test for config and the version command. Does something like container and app make sense? Or maybe container and cli or common and cli? Definitely open to discussion here

I named it vm because the tests there are more concerned about the VM itself instead of the container development functionalities it provides. Open to other names though.

[pendo324]

I'm good with merging it with these names, we can change them later if we come up with something better