Summary

prefer-numeric-literals detects calls to parseInt() / Number.parseInt() purely by identifier/property name, without checking whether parseInt or Number actually resolve to the global built-ins. If either is shadowed by a local binding, the rule still reports it, and its --fix autofix replaces the call with a numeric literal — silently changing the program's behavior since the call is no longer to the (unrelated) shadowed binding at all.

function parse(parseInt) {
  return parseInt("11", 2); // user's own `parseInt` parameter, not the global
}

--fix turns this into:

function parse(parseInt) {
  return 0b11; // the call disappeared entirely
}

Sibling rules radix and use-isnan were already fixed for the same class of bug (see #21044 and #20958), by checking sourceCode.isGlobalReference(...) in addition to the name-based check. This PR applies the same fix to prefer-numeric-literals.

Test plan

• Added valid test cases for shadowed parseInt (both as a parameter and a var declaration) and shadowed Number (member access form)
• npm test -- tests/lib/rules/prefer-numeric-literals.js passes (91 tests)
• Verified manually with Linter#verify/verifyAndFix that the false positive and the destructive autofix are both gone after the fix