Add a rule to prevent bpmn:Error scopes with missing required properties

[pinussilvestrus]

Is your feature request related to a problem? Please describe

Currently bpmn:Error scopes can be created without required properties. For example, following scoped binding

"scopes": [
  {
    "type": "bpmn:Error",
    "id": "error-1",
    "properties": []
  }
]

would be valid, but would produce an invalid Error in the bpmn-js Properties Panel

<bpmn:error id="Error_error-1_2m10p8r" />

that misses required properties as name and errorCode.

Describe the solution you'd like

Add a rule that checks for required properties.

• name
• errorCode

Example scoped binding

"scopes": [
  {
    "type": "bpmn:Error",
    "id": "error-1",
    "properties": [
      {
        "type": "String",
        "value": "error-code",
        "binding": {
           "type": "property",
           "name": "errorCode"
         }
       },
       {
         "type": "String",
         "value": "error-message",
         "binding": {
            "type": "property",
            "name": "camunda:errorMessage"
           }
       },
       {
         "type": "String",
         "value": "error-name",
         "binding": {
            "type": "property",
            "name": "name"
        }
      }
    ]
  }
]

Describe alternatives you've considered

Keep it as it is.