Constraint validation is handled at the RAML layer. AppDefinition defined a redundant set
of constraint validation rules that added no value and grew out of sync w/ the RAML layer.
This change set removes the constraint validation from AppDefinition and refactors some of
the related unit tests. As part of the test refactoring the constraint violation messages
were tweaked and turned into constants for easier testing.
I only see a reference to mesosphere/marathon/api/v2/validation/SchedulingValidation.scala:112 ??
Where do we use the constraints validator?