fix(linter): detect missing displayName when TS interface shares name with createContext (#19607)

[cobyfrombrooklyn-bot]

Problem

The react/display-name rule with checkContextObjects: true fails to detect a missing displayName when a TypeScript interface or type alias shares the same name as a createContext variable.

import { createContext } from 'react';

interface PostHogGroupContext { value: string; }
const PostHogGroupContext = createContext<PostHogGroupContext | null>(null);
// ^ Should report missing displayName, but doesn't

Root Cause

When interface Foo and const Foo = createContext() share the same name, oxc's semantic binder merges them into one symbol. The interface gets the primary symbol_declaration (since it's declared first). The is_react_component_node function receives the interface's AST node, finds no matching arm (it handles VariableDeclarator, FunctionDeclaration, etc. but not TSInterfaceDeclaration), and returns None. The code then falls through to check_context_assignment_references which checks write references, but a const initializer isn't a write reference.

Fix

When the primary declaration isn't a component, also check the symbol's redeclarations via ctx.scoping().symbol_redeclarations(). If a redeclaration (e.g. the VariableDeclarator with createContext()) is a component, it's detected correctly.

Tests

Added 3 test cases:

1. Fail: Interface + createContext with same name (exact repro from react/display-name: checkContextObjects misses context when TypeScript interface shares the same name #19607)
2. Fail: Type alias + createContext with same name
3. Pass: Interface + createContext with same name but displayName is set

Updated snapshot. cargo test -p oxc_linter --lib -- display_name passes.

Tested locally on macOS ARM (Apple Silicon).

[camc314]

duplicate of #19608