Improve force layout

[flo-dup]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

Does this PR already have an issue describing the problem ?
No

What kind of change does this PR introduce?
Bug fix and layout improvements

What is the current behavior?
Unwanted behavior of force-layout algorithm:

• counting twice some edges as direction does matter in equals
• repulsion is added twice on each (node,node) pair
• when two nodes are very close at one step they slow down the algorithm as they are sent very far apart
• the damping term helps the convergence but does not make sense physically
• the default parameters of the algorithm do not fit the usual use cases of network-area-diagram

What is the new behavior (if this is a feature change)?

• edges not counted twice even if adding an equivalent edge reversed
• repulsion only added once on each (node,node) pair
• when two nodes are very close at one step they are not sent too far apart
• the damping term has been replaced with a friction
• the default parameters fit better the usual use cases of network-area-diagram; nonetheless the stiffness needs to be adapted for very large networks (set to 100)

Does this PR introduce a breaking change or deprecate an API? Yes

• The Breaking Change or Deprecated label has been added
• The migration guide has been updated in the github wiki (What changes might users need to make in their application due to this PR?)

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

72.2% Coverage
0.0% Duplication