In service-binding-operator we currently have a mix of scripting in ./hack and scripting in .travis.yml and Makefile itself. And we need to start moving this "logic" to standalone components, as in standalone scripts in hack directory.

The reason for this organizational move is to make it easy to isolate the pieces of automation into unique places, and also make it simple by reproducing those actions in developers' laptops, without need to trigger a whole new job in Travis-CI.

Furthermore, Makefile should become the driver for automation routine, therefore, .travis.yml should not contain any direct commands, but instead invoke an make target.

And in Makefile we should keep it as concise as possible, and for every target that would require more than a couple commands, it should become a "hack script" instead.

Changes

To recap, the changes described on this ticket are the following:

• Remove all scripting from .travis.yml moving them into ./hack scripts;
• Only use Makefile targets in Travis-CI, never commands or scripts directly;
• Remove long stream of commands from Makefile, move them as ./hack scripts as well;

Acceptance Criteria

Upstream pull-request with following our definition of done.