Wire the WhatsApp tree-sitter-erlang grammar into the extraction pipeline
with a custom visitNode extractor that handles Erlang's fun_decl/function_clause
AST structure. Extracts modules, functions, records, type/opaque declarations,
macros, imports/includes, exports, and call edges. Benchmarked on poolboy,
cowboy, and EMQX — codegraph reduces file reads to zero across all three.

Erlang remote calls like `gen_server:call(...)` now emit qualified
`module:function` references that resolve to functions in the target
module file. On cowboy, this creates 793 cross-file call edges where
previously all calls were file-local.
- extractCall: detect `call` nodes inside `remote` parents and emit
 `module:function` as the callee name
- import-resolver: add resolveErlangRemoteCall() that matches the
 module prefix to the target .erl file stem
- test: verify gen_server:start_link, gen_server:call, my_db:lookup
 are extracted as qualified references

Erlang -behaviour(gen_server). now creates module→behaviour implements
edges instead of import nodes. For in-project behaviours, the edge
resolves to the actual module; for OTP stdlib behaviours, the reference
stays unresolved rather than mis-connecting to a same-named field.
On cowboy, this produces 27 correct implements edges (e.g.
cowboy_router → cowboy_middleware). A callback synthesizer bridges
behaviour function dispatch for in-project behaviours.
- erlang.ts: behaviour_attribute emits implements unresolved reference
- import-resolver: resolveErlangBehaviourImplements matches module nodes
- index.ts: skip name-matcher for Erlang implements (wrong edge > missing)
- callback-synthesizer: erlangBehaviourEdges bridges dispatch + adds
 erlang to IFACE_OVERRIDE_LANGS

Parse .app.src / .app files as Erlang, extracting the application name
as a module node and the applications list as import nodes for
inter-app dependency tracking.

Connect -include/-include_lib directives to their target .hrl files
via file→file imports edges. Resolves same-directory includes first,
then falls back to project-wide search.

...queries
The pre-filter, symbol lookup, and CLI commands all handled '.', '::',
and '/' separators but missed Erlang's single-colon 'module:function'
syntax. This caused 'mdb:dirty_insert' references to be dropped before
the Erlang remote call resolver could match them, and made callers/
callees/impact return empty results when queried with the qualified name.