Control Interface stests workload must be build and pushed automatically on every change

[krucod3]

Description

With #22 and the PR #324 we have added a container that acts as a workload communicating over the Control Interface.
The target of this container is to execute a system test against the Control Interface and check if everything is working as expected.

The container and the app inside are currently build and pushed manually.
We would like to automate this process, see below for a solution sketch.

Goals

The goal of this ticket is to automate the building and pushing process of the containerized test app.

Final result

Summary

The Control Interface test app container shall be build on every change of:

• the Control Interface (at least changes in control_api.proto, ank_base.proto, build.rs, src/*, )
• the test app itself (at least Cargo.lock, src/*, Dockerfile)
  A hash can be build out of all dependencies specified above and a check can be done in every CI/CD build if a container with a version corresponding to this hash exists. If not the container has to be rebuild and pushed.

The stests must be updated to use the container that corresponds to the current hash build from the file listed above. (This building of the hash shall be done by some common code/bash script)

The version of the container can be the hash itself.

The benefits of the solution is that a container for a certain version would be build just once and not on every commit

Tasks

• Task 1
• Task 2
• ...