Remove deprecated APIs (#5167)

* Remove deprecated APIs

Summary:
Mirrors the cleanup of deprecated APIs that were recently removed. See react/react-native#57384 for the list

* Update statusbar.md

* Fix prettier errors

Author: Abbondanzo

docs/animated.md

@@ -216,7 +216,7 @@ Config is an object that may have the following options:
 
 - `velocity`: Initial velocity. Required.
 - `deceleration`: Rate of decay. Default 0.997.
-- `isInteraction`: Whether or not this animation creates an "interaction handle" on the `InteractionManager`. Default true.
+- `isInteraction`: Whether or not this animation creates an "interaction handle". Default true.
 - `useNativeDriver`: Uses the native driver when true. Required.
 
 ---
@@ -234,7 +234,7 @@ Config is an object that may have the following options:
 - `duration`: Length of animation (milliseconds). Default 500.
 - `easing`: Easing function to define curve. Default is `Easing.inOut(Easing.ease)`.
 - `delay`: Start the animation after delay (milliseconds). Default 0.
-- `isInteraction`: Whether or not this animation creates an "interaction handle" on the `InteractionManager`. Default true.
+- `isInteraction`: Whether or not this animation creates an "interaction handle". Default true.
 - `useNativeDriver`: Uses the native driver when true. Required.
 
 ---
@@ -271,7 +271,7 @@ Other configuration options are as follows:
 - `restDisplacementThreshold`: The threshold of displacement from rest below which the spring should be considered at rest. Default 0.001.
 - `restSpeedThreshold`: The speed at which the spring should be considered at rest in pixels per second. Default 0.001.
 - `delay`: Start the animation after delay (milliseconds). Default 0.
-- `isInteraction`: Whether or not this animation creates an "interaction handle" on the `InteractionManager`. Default true.
+- `isInteraction`: Whether or not this animation creates an "interaction handle". Default true.
 - `useNativeDriver`: Uses the native driver when true. Required.
 
 ---

docs/animations.md

@@ -669,4 +669,4 @@ As mentioned [in the Direct Manipulation section](legacy/direct-manipulation), `
 
 We could use this in the Rebound example to update the scale - this might be helpful if the component that we are updating is deeply nested and hasn't been optimized with `shouldComponentUpdate`.
 
-If you find your animations with dropping frames (performing below 60 frames per second), look into using `setNativeProps` or `shouldComponentUpdate` to optimize them. Or you could run the animations on the UI thread rather than the JavaScript thread [with the useNativeDriver option](/blog/2017/02/14/using-native-driver-for-animated). You may also want to defer any computationally intensive work until after animations are complete, using the [InteractionManager](interactionmanager). You can monitor the frame rate by using the In-App Dev Menu "FPS Monitor" tool.
+If you find your animations with dropping frames (performing below 60 frames per second), look into using `setNativeProps` or `shouldComponentUpdate` to optimize them. Or you could run the animations on the UI thread rather than the JavaScript thread [with the useNativeDriver option](/blog/2017/02/14/using-native-driver-for-animated). You may also want to defer any computationally intensive work until the JS thread is idle (for example, with `requestIdleCallback`). You can monitor the frame rate by using the In-App Dev Menu "FPS Monitor" tool.