Improve performance by avoiding repeated recalculateRenderedStyle #3309

[YinDongFang]

Cross-references to related issues. If there is no existing issue that describes your bug or feature request, then create an issue before making your pull request.

Associated issues:

• Repeated renderings of edges and O(n²) complexity when rendering multiple Bezier edges #3309

Notes re. the content of the pull request. Give context to reviewers or serve as a general record of the changes made. Add a screenshot or video to demonstrate your new feature, if possible.

• Avoid repeated render to improve performance.
  In my local environment, redraw time descrease from 130-140ms to 5-9ms when parellel bezier edges count is 100.
  redraw time descrease from 3200-3400ms to 25-35ms when parellel bezier edges count is 500.

Checklist

Author:

• The proper base branch has been selected. New features go on unstable. Bug-fix patches can go on either unstable or master.
• Automated tests have been included in this pull request, if possible, for the new feature(s) or bug fix. Check this box if tests are not pragmatically possible (e.g. rendering features could include screenshots or videos instead of automated tests).
• The associated GitHub issues are included (above).
• Notes have been included (above).

Reviewers:

• All automated checks are passing (green check next to latest commit).
• At least one reviewer has signed off on the pull request.
• For bug fixes: Just after this pull request is merged, it should be applied to both the master branch and the unstable branch. Normally, this just requires cherry-picking the corresponding merge commit from master to unstable -- or vice versa.

[maxkfranz]

This needs to have the IDs sorted, because a bezier bundle can contain edges that go in either direction, e.g.

E1: A -> B
and
E2: B ->A
could both be in the same bundle