Cleanup usage of weight in plugin config
Problem/Motivation
If you take a look at the position of the Negate the condition select field across Tasks and SequenceFlows you will notice that its position varies. Most of the time you will find it at the end of the list of custom properties for a template (talking in bpmn terminology here), then a few times at the top and then few times somewhere in between.
Proposed resolution
Since it is a setting that inverts the made configuration imho it should be placed more prominently as well as consistently. i would go either with on top or at the bottom - but i am leaning towards the former - the somewhere in between variant is no option at all imho in any case. by choosing to go with placing it on top the user is aware if it is the standard or the inverted setting upfront before making any settings within the rest of the available configuration options of the template accordingly.
p.s. opened the issue in the eca issue queue, cuz the only code i found in the context of Negate the condition was in ECA source files.