[3604] Make node overlap resolution faster during "Arrange All"

[pcdavid]

• [3604] Update CHANGELOG
• [3604] Only compute if nodes intersect
• [3604] Remove useless test
• [3604] Filter out non-siblings earlier
• [3604] Avoid creating intermediate rectangles

On the following diagram (a simple diagram with recursive nodes for every papaya::NamedElement, created on the "Package java.lang" element in the "Sirius Web" Papaya example), I go from 60s to a little less than 20s.

Note that the first 6s or 7s seem to be spent in ELK? At least during this time I see the loading indicator added in #3574 spinning for these first seconds, and then it stops moving while my CPU is working for the rest of the duration.

The diagram is very specific and does not contain any actual overlap, so it's very possible my changes breaks some stuff. Take with a grain of salt for the moment.

[pcdavid]

After this first batch, a profiling in Chromium shows this:

• First (in red), about 7s waiting for the backend for the result of the mutation layoutDiagram() operation.
• Then (in blue), about 13s trying to detect and resolve overlaps (which do not exist in this case).

I'm wondering if the backend could pre-compute some of the required information? Even just a flag indicating if there are any overlap so that the front could simply avoid all of this in the (common?) case where there are none.