Adding swimlanes for optical logic encapsulation

Just noticed that this is the wrong place here and we need to move it to bpmn_io.

@mysdiir you can easily give this a try by deleting the following 2 lines from the bpmn_io.css file:

72: .djs-palette-entries .bpmn-icon-participant,
79: .djs-context-pad .bpmn-icon-participant,

Visually, that should already be all that's required. But we need to test of saving and executing models, where plugins are contained in such "participants" will still work as expected.

Ah, just tested a bit and it's not that simple because the XML structure changes completely. Each "participant" is treated like a model of its own, i.e. pretty much as if multiple ECA models were contained in a single one. That requires us to re-architect the \Drupal\eca_modeller_bpmn\ModellerBpmnBase class.

This is now implemented in the 3.x branch. The caveat at this time is that the swim lanes (called participants in BPMN) will only be stored in the raw XML data of BPMN, but not in the ECA config entity. Therefore, if the raw data won't be stored (a new option with Modeler API), then the participants will be lost, but the model itself still remains intact.

Automatically closed - issue fixed for 2 weeks with no activity.