Migrate react-hooks/react-compiler to split up rules

[karlhorky]

The react-hooks/react-compiler rule was split up into separate rules to offer clearer feedback to developers:

• docs(eslint-plugin-react-hooks): document react-hooks/react-compiler rule facebook/react#34117 (comment)

Migrate to all of the new rules listed as available in the RC section of the eslint-plugin-react-hooks docs page, except for incompatible-library, because this rule is not yet available:

• Bug: react-hooks/incompatible-library not found facebook/react#34632

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[karlhorky]

Consider whether some of these strict React Compiler rules react-hooks/set-state-in-effect, react-hooks/set-state-in-render and react-hooks/purity should be disabled, because they're too hard to adhere to:

• [feat] New rule react-x/no-circular-(use)-effect to detect circular set functions and deps patterns in useEffect like hooks Rel1cx/eslint-react#755 (comment)

For example, consider instead disabling react-hooks/set-state-in-effect in favor of eslint-plugin-react-you-might-not-need-an-effect

• Consider usage of eslint-plugin-react-you-might-not-need-an-effect #516