feat(parser): track JSX elements as function calls for intra-file resolution

[rafalemosmarta]

Problem

JSX elements (<Foo />, <Bar>...</Bar>) are not tracked by the TypeScript
parser as function calls. This causes false positive dead code reports for
React components defined and used within the same file — a very common pattern
in TSX codebases.

The root cause is that tree-sitter models JSX tags as jsx_element /
jsx_self_closing_element nodes, not call_expression, so they were invisible
to the call tracing pipeline.

Solution

Added _extract_jsx_usage() to the TypeScript parser:

• Dispatches on jsx_element and jsx_self_closing_element in _walk()
• Converts uppercase tag names to CallInfo records (same as function calls)
• Skips native HTML tags (lowercase: <div>, <span>, etc.)
• Supports dotted components (<Form.Input />) via receiver field

Tests

Added 6 test cases covering:

• Self-closing elements (<Foo />)
• Opening/closing elements (<Foo>...</Foo>)
• HTML tag filtering (lowercase skipped)
• Dotted components (<Ns.Component />)
• Nested components
• Mixed JSX + regular function calls

All 25 tests pass (19 existing + 6 new).