[react-compiler] Skip hook validation for method calls on untyped module imports

[sleitor]

Summary

Third-party libraries like amCharts export objects with methods named useTheme(), useData(), etc. that are not React hooks. The React Compiler's ESLint plugin incorrectly flags these as hook violations because the hook detection heuristic treats any use*-named property as a potential hook.

This change tracks identifiers loaded from module imports (ImportDefault, ImportNamespace, ImportSpecifier) whose types are unresolved by the type system. For MethodCall instructions where the receiver is one of these untyped imports, we skip hook validation since the use* property was typed heuristically based on naming alone, not from actual type info.

How it works

In ValidateHooksUsage.ts:

1. Track untyped import identifiers: During LoadGlobal processing, we record identifiers that come from import bindings but have unresolved types (not Object or Function with known shapes).

2. Skip hook validation for MethodCalls on untyped imports: When processing a MethodCall, if the receiver is an untyped import, we skip the hook conditional/dynamic usage checks.

3. Handle nested function expressions: In visitFunctionExpression, we similarly skip hook-in-callback validation for method calls on untyped receivers.

What's preserved

• import React from 'react'; React.useState() — React has a known type, so hook validation is preserved ✅
• const React = require('react'); React.useState() — React is a ModuleLocal binding (not an import), so it's not tracked as an untyped import and hook validation is preserved ✅
• Direct hook calls like useHook() — These are CallExpressions, not MethodCalls, so they're unaffected ✅
• import {useHook} from 'some-lib'; useHook() — Direct import of a hook-named function still validates correctly ✅

Test plan

• All 1711 existing compiler snap tests pass
• All 30 ESLint plugin tests pass
• Manual testing confirms:
  • amCharts.useTheme() in conditional blocks no longer errors
  • React.useState() in conditional blocks still errors (both import and require styles)
  • Direct useHook() calls in conditional blocks still error

Fixes #32109

[josephsavona]

ooops, meant to reply to a different PR that you sent today.