Add initial pool and swimlane implementation

[matthiaslehnertum]

This PR intends to add support for pools and swimlanes to the BPMN diagram type.

Checklist

• I documented the TypeScript code using JSDoc style.
• I added multiple screenshots/screencasts of my UI changes
• I translated all the newly inserted strings into German and English

Motivation and Context

Pools are swimlanes are central components of the BPMN standard, allowing to model activities of different operators and their exchanges.

Description

Pools are added to the BPMN diagram type as a new entity type with the ability to add swimlane within it.

Steps for Testing

1. Select the BPMN diagram type
2. Drop a pool element onto the canvas
3. Double click on the pool element
4. Add a few swimlanes
5. Try resizing the swimlanes
6. Add elements within the swimlanes and connect them
7. Delete one of the swimlanes

Test Coverage

File	% Stmts	% Branch	% Funcs	% Lines
main/packages/bpmn/bpmn-pool	49.58	100	40	49.58
bpmn-pool-component.tsx	100	100	100	100
bpmn-pool-update.tsx	38.4	100	0	38.4
bpmn-pool.ts	40.32	100	50	40.32
main/packages/bpmn/bpmn-swimlane	89.65	100	66.66	89.65
bpmn-swimlane-component.tsx	100	100	100	100
bpmn-swimlane.ts	81.81	100	50	81.81

Screenshots

Example of a BPMN diagram with a pool with multiple swimlanes

Example of the update dialog of the pool that allows inserting additional swimlanes

[loreanvictor]

One final note: how can I disassociate a BPMN element from a pool? I can drag an element into a pool and they are associated (e.g. they move together), but dragging them outside of the pool won't disassociate the elements. This is in contrast to behaviour of similar elements in other diagram types (e.g. packages in class diagrams) where I can drag a child element out of a parent element to disassociate them.

[matthiaslehnertum]

@loreanvictor I would merge the Groups PR first - that one fixes the disassociation issue for the pools and swimlanes as well

[AlexanderG2207]

Everything works well locally with adding lanes and adding elements to the lanes. However, the resizing of the pool gives me issues, especially when trying to resize the bottom lane.

[loreanvictor]

a few issues I've found on:

• the zoomFactor property error appears again, perhaps it was fixed on some other elements? it happens when adding a pool.

  

• management of lanes in a pool differs from management of other "child elements": to add a lane you need to double click on the pool and add them via the context menu, but to manage lanes you need to select lanes individually.

  

  this is in contrast to other elements with children, for example attributes on a class, where the context menu allows adding AND managing children (which seems more intuitive).

  

  of course this second point is a UX issue not an actual issue, so it could also be further discussed and if it really needs to be changed / updated, that can happen via a subsequent PR.

p.s. in addition to these issues, one of the tests is still failing.

[loreanvictor]

Ok all the previous issues are nicely resolved and the tests are passing, manual testing also seems to be fine with the pools and lanes, etc.