📎 Add `reactCompiler` option for `useExhaustiveDependencies`

[arendjr]

Description

useExhaustiveDependencies currently reports a diagnostic when using functions that are not wrapped with useCallback as dependency: “[myFunc] changes on every re-render and should not be used as a hook dependency”.

This diagnostic is not accurate for users of the React Compiler, since it automatically wraps such functions.

To resolve this, I agree with this comment that we should introduce an option for this.

Before starting work on this, I think we need to agree what to call the option and where to place it. I think having a single reactCompiler option makes sense, so that if we need other changes to accommodate the React Compiler users still only need to set one option. But that leaves the question whether it should be on the useExhaustiveDependencies rule, or if other React-related rules may also benefit from this, in which case we may prefer to move it up. Suggestions welcome!

[tusharsnx]

Would it be good enough to split useExhaustiveDependencies into two buckets, one with "[myFunc] changes on every re-render and should not be used as a hook dependency" warning, and another with whatever is left of useExhaustiveDependencies?

The first rule can be manually disabled for now. In the future, based on some heuristics we can disable it by-default when the react-compiler is detected.

[arendjr]

@tusharsnx I think that's quite a sensible suggestion!

Note I'm also addressing your suggestion in #5486, since it might be a good use case for a reactCompiler domain.