Skip layer invalidation when an iOS View only changes opacity

An opacity change set `needsInvalidateLayer`, so `finalizeUpdates:` ran the
whole `invalidateLayer`: shadow path, borders, and the background,
box-shadow, outline and mask layers. `invalidateLayer` reads the opacity
only to combine it with `filter`, and the new opacity is already applied to
the layer in `updateProps:`, so the invalidation is now requested only when
the view has a filter. Native-driver and Reanimated opacity animations
update every animated view on every frame, so each styled view paid the
full invalidation per frame.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: hryhoriiK97

packages/react-native/React/Fabric/Mounting/ComponentViews/View/RCTViewComponentView.mm

@@ -355,7 +355,10 @@ - (void)updateProps:(const Props::Shared &)props oldProps:(const Props::Shared &
   if (oldViewProps.opacity != newViewProps.opacity &&
       ![_propKeysManagedByAnimated_DO_NOT_USE_THIS_IS_BROKEN containsObject:@"opacity"]) {
     self.layer.opacity = (float)newViewProps.opacity;
-    needsInvalidateLayer = YES;
+    // `invalidateLayer` only reads the opacity to combine it with `filter`.
+    if (!newViewProps.filter.empty()) {
+      needsInvalidateLayer = YES;
+    }
   }
 
   // Disable `removeClippedSubviews` when Fabric View Culling is enabled.