linter: no_obj_calls stackover

[Boshen]

From #4212

This has a semantic error, but should not panic nevertheless.

export const getConfig = getConfig;
getConfig();

cargo run -p oxlint -- -A all -D no-obj-calls test.ts

thread '<unknown>' has overflowed its stack
fatal runtime error: stack overflow

Git blamed to a year ago, thank you @DonIsaac for being part of us for more than a year.