Deployer should use Fabric8's Container validations

[cppwfs]

Fabric8 Container class currently has constraints enumerated for its attributes.
i.e. for valid schedule name expression and maximum length.
We need to capture these ConstraintValidationExceptions when thrown, and wrap them with a meaningful message.
Currently we explicitly check for these in the validateScheduleName method, which seems forced.
Currently the hibernate validator in unit tests doesn't check the constraints enumerated in the Container class.