E2E: Fix GridRowScrollPinning Registration and DOM Lookup Flaws

This ticket documents and summarizes the critical bug fixes and architectural cleanups applied to the GridRowScrollPinning Main Thread addon and its integration with the ScrollManager to resolve initial integration failures.

Completed Fixes & Cleanups:

1. Registration Fix (ScrollManager): The initial implementation guarded the registration inside afterSetRowScrollPinning with if (oldValue !== undefined). Because the config defaults to true, this prevented the addon from ever registering. The guard was removed.
2. Missing Action Property Support (GridRowScrollPinning): Neo.vdom.Helper.compareAttributes does not explicitly set action: 'updateNode' on deltas, relying on the main thread to default to it. The addon's strict check delta.action === 'updateNode' caused it to ignore all incoming row updates. The check was updated to (!delta.action || delta.action === 'updateNode').
3. Negative Scroll Transform Support (Regex): When rows are recycled and moved out of bounds, the App Worker can calculate negative Y transforms (e.g., translate3d(0px, -50px, 0px)). The initial regex \d+ only matched positive integers, causing negative transform strings to be ignored, resulting in massive row overlapping. The regex was updated to /-?\d+(?:\.\d+)?/ and parsing was switched to parseFloat.
4. Targeting the Correct DOM Node for ScrollTop: The original implementation queried the outer grid-body node for scrollTop, which was always 0. The addon was updated to explicitly append the __wrapper suffix to target the internal scrollable container node (DomAccess.getElement(registration.bodyId + '__wrapper')).
5. Performance & Architectural Cleanup:
   • The translateRegex was extracted to a module-level constant to prevent expensive recompilation on every row iteration.
   • Reverted a temporary hack in ScrollManager that passed the __wrapper suffix in the registry ID, restoring the clean bodyId registry pattern.