Error states with error types should not be triggered by error events without types or non-matching types

[reteprelief]

Error states can be defined to be error type specific, i.e., they carry an error type from a specified list of allowable types.
Either the type is explicitly specified in the target state specification, or the target state specification is without type. In that case the error type of the error event is used. In that case the error type of the error event must be contained in the set of error type specified with the state. Furthermore, an error event without a type cannot trigger the transition if the target state is expected to carry a type.

OSATE should provide a validation to inform the user of this issue. Furthermore, the fault trace/tree generation should not include an error event that cannot trigger the state carrying types.