Description of problem: 

I did a mistake when writing my tests, and I was sending scheduleId instead of measurementDefinitionId when creating alert with condition where measurementDef is required.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. do POST /rest/alert/definitions?resourceId=10001
with body

{"dampeningCategory": "NONE", "conditions": [{"category": "BASELINE", "threshold": "0.2", "measurementDefinition": <MID>, "option": "max", "comparator": "<"}], "conditionMode": "ALL", "enabled": true, "name": "rest-condition-incorrect-mdef"}

where <MID> is measurementDefinnitionId valid ID, but not related to 10001's resource type (it's measurementDef for different resource type)


Actual results: alert with such condition is created -it's invalid and such alert would never get triggered


Expected results: server must reject condition with such measurementDefId


Additional info: