Rule blocked: CG0011A2 - please extend "non_conformant_xxx" operators for variable (non-VLM) level

The operators:
- [conformant_value_data_type](https://cdisc-org.github.io/conformance-rules-editor/#/check_operator?id=conformant_value_data_type)
- [non_conformant_value_data_type](https://cdisc-org.github.io/conformance-rules-editor/#/check_operator?id=non_conformant_value_data_type)
- [conformant_value_length](https://cdisc-org.github.io/conformance-rules-editor/#/check_operator?id=conformant_value_length)
- [non_conformant_value_length](https://cdisc-org.github.io/conformance-rules-editor/#/check_operator?id=non_conformant_value_length)

seem only be defined on the VLM level.
For some of the CG0011xx rules, we however need to check e.g. whether --DUR have been correctly defined in the define.xml as of DataType="durationDateTime", and for --DTC variables whether these have correctly been defined as either "date", "dateTime", "time", "partialDate", "incompleteDate" etc..

I think this can be accomplished by extending the above mentioned operators to the "variable level", so not only be applicable to the VLM level. There might then need to be an extra piece of information to state whether the level is "variable" or "valuelist".

Alternatively, one can develop separate such operators which only work at the variable level.

Other alternative is to have an operator like:
name: --DUR
operator: does_not_have_define_datatype
value:
- date
- dateTime
- ...
(and the corresponding operator "has_define_datatype")

P.S. I did not find any use of these 4 operators in any of the YAML yet ...