Describe the bug

I'm working in a monorepo which includes both React and NestJS projects. Nest also exports a function named forwardRef, which the linter over-zealously removes (see the below diff after running eslint --fix

Looking at the rule source, isReactAPI doesn't seem to validate the import actually comes from the react package

I've bypassed it on my end by disabling the rule for that workspace

Reproduction

1. Create a file with the contents

import { forwardRef } from "not-react"

forwardRef(() => null)

2. Run eslint --fix

3. See that the non-react forwardRef has been removed

Expected behavior

Only react APIs are removed

Platform and versions

"@eslint-react/eslint-plugin": "^1.52.2",

Stack trace

Additional context

No response