Create port conflict scheduler

Figured I would poke around with this and try to implement a simple scheduler that refuses to colocate containers on engines that are already publishing a container on that hostIp:port. This would be useful to compose with other schedulers when you want to schedule a container that binds to a well known port on the host interface.

Feedback welcome :)