[qe] change e2e image to inherit fom deliverest

[adrianriobo]

    The strategy used by the e2e image to run a workload remotely has been generalized through the usage (inherit) from a base image deliverest, the change require now each platform/arch has its own image (identified on the image version) which made the image smaller. Also all best practices when handling remote connections are now inherited from the base image and e2e image resources just define its specific execution steps

Fixes: Issue #N

Relates to: Issue #N, PR #N, ...

Solution/Idea

Describe in plain English what you solved and how. For instance, Added start command to CRC so the user can create a VM and set-up a single-node OpenShift cluster on it with one command. It requires blablabla...

Proposed changes

List main as well as consequential changes you introduced or had to introduce.

1. Add start command.
2. Add setup as prerequisite to start.
3. ...

Testing

What is the bottom-line functionality that needs testing? Describe in pseudo-code or in English. Use verifiable statements that tie your changes to existing functionality.

1. start succeeds first time after setup succeeded
2. stdout contains ... if start succeeded
3. stderr contains ... after start failed
4. status returns ... if start succeeded
5. status returns ... if start failed
6. start fails after start succeeded or after status says CRC is Running
7. ...