Validate container constraints to prevent creation of non-runnable containers

[dcvan24]

Container constraints can be non-existent (i.e., there is no hosts that satisfy such constraint) or contradictory (e.g., one constraint requires the container to be run on host A and the other requires host B, in which case the container is impossible to be provisioned). Neither Marathon nor Chronos validates container constraints, but just leaves containers with invalid constraints waiting and does not report errors. This behavior makes the constraint problems obscure to end users and difficult to debug.