fix(transforms): enable transforms on new arch and fix hit testing on both arches

[Saadnajmi]

Summary

CSS transforms (rotate, scale, translateX, etc.) were not rendering on macOS with the New Architecture (Fabric). This PR fixes the root cause and related issues.

Root Cause

On macOS, NSView has no built-in transform property (unlike UIView on iOS). AppKit's layer-backed view system resets layer.transform to identity during its layout/display cycle. This means any transform set on the layer is silently discarded.

Changes

1. Add transform3D property to RCTUIView with anchor point and hit testing fixes

• Stores the transform in an ivar so it survives AppKit's reset
• Re-applies the transform in updateLayer (called during AppKit's display phase)
• wantsUpdateLayer is conditional on having a custom transform or displayLayer: delegate, so drawRect: still works for text views
• Compensates for macOS layer.anchorPoint defaulting to {0, 0} instead of {0.5, 0.5}, so transforms apply from the view's center
• hitTest: and RCTUIViewHitTestWithEvent use CALayer coordinate conversion, which correctly accounts for layer.transform (NSView's convertPoint:fromView: does not)

2. Use transform3D in Fabric component views

• RCTViewComponentView uses self.transform3D instead of self.layer.transform on macOS
• Removes duplicated anchor point compensation and hitTest: override now handled by RCTUIView

3. Update Paper hit testing callers for transform-aware coordinate conversion

• Updates RCTUIViewHitTestWithEvent callers in Paper architecture to use the new fromView parameter, enabling transform-aware hit testing in old architecture as well

Test Plan

• Verified transforms render correctly on macOS Fabric: rotate, scale, translateX, opacity, combined rotate+scale
• Verified text still renders (conditional wantsUpdateLayer prevents skipping drawRect:)
• Verified hit testing works on transformed views (Pressable with click counters)
• Verified no regression on non-transformed views

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3be34a9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR