* feat: add information about change in React typing

See DefinitelyTyped/DefinitelyTyped#56210.

* chore: change wording

* feat: add information about change in React typing

See DefinitelyTyped/DefinitelyTyped#56210.

* chore: change wording

## Summary

Part of #138222

in @types/react@18 types [have become more
strict](DefinitelyTyped/DefinitelyTyped#56210).
This PR addresses a bunch of easy fixes. The most common are:

### 1 Removal of implicit children

For components that do implement children but relied on their implicit
declaration from React.FunctionComponent or React.Component:

```diff
 interface Props {
+  children?: React.ReactNode;
 }

 class SomeClassComponents React.Component<Props> {
   render() {
     return  <div>{this.props.children}</div>
   }
 }
 const SomeFunctionComponent: React.FunctionComponent<Props> = props => <div>{props.children}</div>
```

or 

```diff
- const SomeFunctionComponent: React.FunctionComponent<Props> = props => <div>{props.children}</div>
+ const SomeFunctionComponent: React.FunctionComponent<React.PropsWithChildren<Props>> = props => <div>{props.children}</div>
```


*Note 1:*
The most common change occurs in unit tests where `renderHook` and
`wrapper` are used. I had to re-type the props so that `children` were
there

```diff
const { result } = renderHook(
         () => {
           return useLicense();
         },
         {
-           wrapper: ({ children }) => (
+           wrapper: ({ children }: React.PropsWithChildren<{}>) => (
             <TestProviders license={license}>{children}</TestProviders>
           ),
         }
       );
```

```diff
- const { result } = renderHook<GetCasesColumn, UseCasesColumnsReturnValue>(
+ const { result } = renderHook<React.PropsWithChildren<GetCasesColumn>, UseCasesColumnsReturnValue>(
       () => useCasesColumns(defaultColumnArgs),
       {
         wrapper: ({ children }) => <TestProviders>{children}</TestProviders>,
       }
     );
```



*Note 2:*
With @types/react@17 the components that don't have any props apart from
`children` I had to use `React.PropsWithChildren<{}>`, whereas in
@types/react@18 the argument becomes optional, so it can be omitted, and
type simpler with `React.PropsWithChildren` without an argument



### 2 `this.context` becomes `unknown` (was `any`)

In a couple of places where `this.context` is used, I had to type it

### 3 `ComponentType` from enzyme is no longer compatible with
`ComponentType` from react

This one is a bummer, but where `wrappingComponent` with enzyme is used
I had to cast it to type from `enzyme`

```diff
- import { mount } from 'enzyme'
+ import { mount, ComponentType } from 'enzyme'

 wrapper = mount(<ClosureOptions {...props} />, {
-       wrappingComponent: TestProviders,
+       wrappingComponent: TestProviders as ComponentType<{}>,
});
```

## Summary

Part of #138222

in @types/react@18 types
DefinitelyTyped/DefinitelyTyped#56210. This PR
addresses a bunch of remaining fixes **(hopefully the last mass ping PR
like this)** The most common are:


### 1 Objects are no longer considered a valid ReactNode

In types@17 the ReactNode typing was too soft, it allowed objects and
functions being passed as ReactNode, e.g.

```
let obj: React.ReactNode = {};
let func: React.ReactNode = () => {};
```

This was by mistake, and this PR mutes most of such cases by simply
casting to a `string` or `ReactNode`.
In some cases, it is worth to follow up and address the raised issues in
a better way (see in comments)


```diff

function MyComponent() {

const error: string | Error = 'Error'

return (
  <div>
-   {error}
+   {error as string}
  </div>
)

}

```


Most common problems are related to rendering errors, where it could be
`string | Error` object rendered directly as a ReactNode. Most often it
is related to alerting framework:

```
export interface RuleFormParamsErrors {
  [key: string]: string | string[] | RuleFormParamsErrors;
}
```

Not sure if there is a better fix then casting, surely not short-term. 

### 2 More `useCallback` implicit any fixes

Follow up to #191659

### 3 `EuiSelect` doesn't have a placeholder prop 

In a couple of places, the `placeholder` prop was removed. This is
because react types were updated and `placeholder` was removed from the
base HTML element, so it highlighted places where `placeholder` prop was
redundant

In React 18 implicit children were removed from components. Components that utilize children need to declare their types directly.

See: DefinitelyTyped/DefinitelyTyped#56210

In React 18 implicit children were removed from components. Components that utilize children need to declare their types directly.

See: DefinitelyTyped/DefinitelyTyped#56210

#79

Summary:
Fixes facebookexperimental/Recoil#1717

Since types/react v18, Implicit `children` was removed from `React.FC`. This change works for types/react v18 and earlier.
DefinitelyTyped/DefinitelyTyped#56210

Pull Request resolved: facebookexperimental/Recoil#1718

Reviewed By: drarmstr

Differential Revision: D35501855

Pulled By: mondaychen

fbshipit-source-id: cf469b96a5220966718270e43e3f0503e144acf3

* feat: add information about change in React typing

See DefinitelyTyped/DefinitelyTyped#56210.

* chore: change wording

* feat: add information about change in React typing

See DefinitelyTyped/DefinitelyTyped#56210.

* chore: change wording

* feat: add information about change in React typing

See DefinitelyTyped/DefinitelyTyped#56210.

* chore: change wording

* feat: add information about change in React typing

See DefinitelyTyped/DefinitelyTyped#56210.

* chore: change wording

* feat: add information about change in React typing

See DefinitelyTyped/DefinitelyTyped#56210.

* chore: change wording

* feat: add information about change in React typing

See DefinitelyTyped/DefinitelyTyped#56210.

* chore: change wording

* feat: add information about change in React typing

See DefinitelyTyped/DefinitelyTyped#56210.

* chore: change wording

* feat: add information about change in React typing

See DefinitelyTyped/DefinitelyTyped#56210.

* chore: change wording

* feat: add information about change in React typing

See DefinitelyTyped/DefinitelyTyped#56210.

* chore: change wording

Refs: DefinitelyTyped/DefinitelyTyped#56210

* feat: add information about change in React typing

See DefinitelyTyped/DefinitelyTyped#56210.

* chore: change wording

* feat: add information about change in React typing

See DefinitelyTyped/DefinitelyTyped#56210.

* chore: change wording

* feat: add information about change in React typing

See DefinitelyTyped/DefinitelyTyped#56210.

* chore: change wording