chore(context-pad): update position once per frame

[nikku]

Proposed Changes

As shown in this flame graph, in a huge diagram, we spend substantial amount of time to re-compute canvas viewport (after select) and determine context pad position (to update it):

All this happens within the user transaction, and blocks UI interactivity.

With this PR we batch position updates as we batch visibility updates; we'll otherwise force the browser into expensive in-frame repaints:

Related to #915, camunda/camunda-modeler#4335.

Checklist

To ensure you provided everything we need to look at your PR:

• Brief textual description of the changes present
• Visual demo attached
• Steps to try out present, i.e. using the @bpmn-io/sr tool
• Related issue linked via Closes {LINK_TO_ISSUE} or Related to {LINK_TO_ISSUE}

[marstamm]

I could not break it, great performance improvement!

[marstamm]

Unrelated to this PR, but it seems like the scheduler tests consistently fail on CI Linux

[nikku]

Follow-up to the Firefox test failures: #921.