Fabric: Empty (no-op) layoutSubviews method was removed from RCTComponentView.

Summary:
The method does not do anything besides calling a super method. Even if this method does nothing special, overriding it can have negative performance implications.

Changelog: [Internal] Fabric-specific internal change.

Reviewed By: sammy-SC

Differential Revision: D22309895

fbshipit-source-id: bd8237d15df20017629223f278b1b6ac628b0cc7

Author: shergin

React/Fabric/Mounting/ComponentViews/View/RCTViewComponentView.mm

@@ -53,18 +53,6 @@ - (void)setContentView:(UIView *)contentView
   }
 }
 
-- (void)layoutSubviews
-{
-  [super layoutSubviews];
-  // Consider whether using `updateLayoutMetrics:oldLayoutMetrics`
-  // isn't more appropriate for your use case. `layoutSubviews` is called
-  // by UIKit while `updateLayoutMetrics:oldLayoutMetrics` is called
-  // by React Native Renderer within `CATransaction`.
-  // If you are calling `setFrame:` or other methods that cause
-  // `layoutSubviews` to be triggered, `_contentView`'s and `_borderLayout`'s
-  // frames might get out of sync with `self.bounds`.
-}
-
 - (BOOL)pointInside:(CGPoint)point withEvent:(UIEvent *)event
 {
   if (UIEdgeInsetsEqualToEdgeInsets(self.hitTestEdgeInsets, UIEdgeInsetsZero)) {