Consider combining this repo with `simphony-remote-docker-base`

[peterzahemszky]

In order to simplify CI and reduce maintenance costs, we should consider combining this repo with simphony/simphony-remote-docker-base.

Alternatively, we could introduce versioning to both repos and maintain a clear dependency hierarchy between them.

From #7 (review):

[...] this CI is pulling in latest version of master for simphony/simphony-remote-docker-base and is therefore dependent on state of another repo. We could resolve this by:

• including versioning in each repo to fix reps
• combining both repos to a single simphony-remote-docker that contains a single CI