fix(iOS): do not force accessibilityRespondsToUserInteraction on recycle

Its UIKit default is not a fixed YES but derived from other
accessibility properties (UIAccessibility.h: "default == derived from
other accessibility properties", e.g. NotEnabled elements return NO).
Writing an explicit constant on recycle would permanently replace the
derived behavior, so move it to the skipped-on-purpose list alongside
isAccessibilityElement and accessibilityTraits.

Author: doracawl

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

@@ -744,14 +744,18 @@ - (void)prepareForRecycle
   //     UIImageView whose natural a11y behavior would be clobbered
   //     by forcing NO / None here. Per-subclass reset is a separate
   //     follow-up.
+  //   * `accessibilityRespondsToUserInteraction` — its UIKit default is
+  //     not a fixed value but "derived from other accessibility
+  //     properties" (per the UIAccessibility.h header; e.g. an element
+  //     with UIAccessibilityTraitNotEnabled returns NO). Writing any
+  //     explicit value here would replace the derived behavior with a
+  //     constant, which is worse than the staleness it would fix.
   self.accessibilityElement.accessibilityLabel = nil;
   self.accessibilityElement.accessibilityLanguage = nil;
   self.accessibilityElement.accessibilityHint = nil;
   self.accessibilityElement.accessibilityValue = nil;
   self.accessibilityElement.accessibilityViewIsModal = NO;
   self.accessibilityElement.accessibilityElementsHidden = NO;
-  // UIView default for accessibilityRespondsToUserInteraction is YES.
-  self.accessibilityElement.accessibilityRespondsToUserInteraction = YES;
   self.accessibilityIgnoresInvertColors = NO;
   // Clear only the `accessibilityState` bits the setter writes via
   // self.accessibilityTraits (.NotEnabled / .Selected). Subclass