Include docker-compose launch in the test runner

[kmazurek]

Subtasks:

Compose:

• provide a way for specifying custom compose files
• create a manager module for docker-compose
• re-use already built images (conditional --build flag on docker-compose)
• address original review comments

GH Actions:

• update integration Actions workflow
• provide GitHub token through an env variable

Misc:

• add printing a list of running containers and network info
• update README

Optional:

• wait for specific log lines in compose containers

In the current setup, running integration tests requires a docker-compose network to be started beforehand. This external dependency introduces unnecessary complexity to the test flow.
This can be simplified by managing docker-compose by the test harness runner itself (see test integration workflow for steps which are performed before a test run).