schemas: Fix jobdefinition.priority validation
schemas: Fix jobdefinition.priority validation

When we specify the priority option with dcictl jobdefinition-create,
we always get an error on this field validation (even if the value
is between 0-100.

{
  "status_code": 400,
  "message": "Request malformed",
  "payload": {
    "errors": {
      "priority": "not a valid priority integer (must be beetween 0 and 1000)"
    }
  }
}

This patch fixes the validation in order to coerce the priority value
to an integer.

Change-Id: I0d1f763deb5a040d698bae4ad7762a754c9942be

redhat-cip/dci-control-server,enovance/dci-control-server,redhat-cip/dci-control-server,enovance/dci-control-server