Distinguish Router container from Peer container and create custom Dockerfile for each

[mkrupczak3]

Currently, the Router and the Peers are based off the same Dockerfile (custom container), where a simple environment variable determines their mode of operation at runtime.

Given the expanding complexity with pt. 2 of the project, It will serve us well to create a distinct Dockerfile for each the Router and Peer, in their own subfolder of the project. This will allow us to iterate more quickly and more carefully consider the finer protocol details of implementation.

@kfajdsl @bsolon524