[INFRA] prod - Bump mxgraph from 4.1.0 to 4.2.2

[tbouffard]

Finally, it makes the bump happen as there are no more side effects since we removed the Segment Connector configuration.
The new version of mxGraph slightly improves the position of the labels by moving them to the left which is more accurate regarding the values in the BPMN diagram.

The custom mxGraph extensions have been migrated

• ShapeConfigurator
  • mxSvgCanvas2D.prototype.getTextCss: no change since 4.1.0 https://github.com/jgraph/mxgraph/blame/v4.2.2/javascript/src/js/util/mxSvgCanvas2D.js#L1472
  • mxShape.prototype.createSvgCanvas: no structural change except the Firefox hack that has been removed (already commented) - https://github.com/jgraph/mxgraph/blob/v4.2.2/javascript/src/js/shape/mxShape.js#L622
  • mxCellRenderer.prototype.createCellOverlays: no change - https://github.com/jgraph/mxgraph/blob/v4.2.2/javascript/src/js/view/mxCellRenderer.js#L543
• MxGraphCustomOverlay our implementation is based on mxCellOverlay.prototype.getBounds: no change in https://github.com/jgraph/mxgraph/blob/v4.2.2/javascript/src/js/view/mxCellOverlay.js since v3.4.0

Tests and screenshots

• All screenshots have been done with Chromium 100.0.4863.0 (Playwright 1.19.2) on Ubuntu 20.04.4 LTS.
• The thresholds configuration has been adapted
  • most of the thresholds are now using a syntax closed to the percentage value i.e 0.02 / 100 instead of 0.0002. This improves readability for comparison with the actual percentage value found in the test report. This will also easily switch to the direct percentage value in the future (direct usage of 0.02 in the previous example)
  • some thresholds have been fixed. They were previously 100 times larger than the right value (they were missing the 100 divisor). For instance, in bpmn.rendering.test.ts, the Firefox 'labels.01.general' threshold on windows was 13.53, it is now fixed to 13.42 / 100. These errors were recently introduced when removing the 'no orthogonal segments' (refs [FIX] Do not force usage of orthogonal edge segments #1868).

Notes

This PR is a new attempt after #502, #547, #1784 (commits of 1784 have been reused here)
closes #321
closes #919

[github-actions]

♻️ PR Preview 2e2f280 has been successfully destroyed since this PR has been closed.

_{🤖 By surge-preview}

[github-actions]

♻️ PR Preview 2e2f280 has been successfully destroyed since this PR has been closed.

_{🤖 By surge-preview}

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[csouchet]

Very good job for the upgrading of mxGraph 🎉 👍🏻

[github-actions]

Pull request title linting 🚨

In order to merge this pull request, the title of the pull request should be prefixed by one of the available types.

Available types:

• feat: A new feature
• fix: A bug fix
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• refactor: A code change that neither fixes a bug nor adds a feature
• perf: A code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit

---

Examples

feat(grpc): add new endpoint
refactor: combine class A and class B
ci: update pull request linter
style: change format of strings

💁 For more examples, visit https://www.conventionalcommits.org/en/v1.0.0/#examples.