Implement subprocess expansion if deployment model is too big

[wiomoc]

ref: #31

[LaviniaStiliadou]

Seems not to work for me.

If I reload the topology, the edges are there but the subprocess is not expanded

[KuhnMn]

I added a small improvement for the Smart Edges here. I noticed that the sorting by y only meant that edges coming from or going to the bottom or top still overlapped a lot, the example topology I had was barely decipherable, so I adjusted it. Might be better to move this to a different PR though or remove it if unwanted.

[wederbn]

Expanding the deployment model looks good in general, however, the margins are a bit too large:

Collapsing the deployment models leaves the subprocesses in the state with the expanded size:

[LaviniaStiliadou]

I think that the current implementation does not consider a change of the deployment model. For example if I change the CSAR (where the deployment model is bigger) then the subprocess does not change size.

[LaviniaStiliadou]

I think the margins are not right when explanding the deployment model. The topology nodes are outside the subprocess

[LaviniaStiliadou]

If the option: "No CSAR" is selected, the size of the subprocess does not change back.

[wederbn]

Closed, as the edges are currently not smart enough and lead to overlaps