LLD doesn't handle `--warn-unresolved-symbols` the same as GNU LD

While upgrading tursodb to rust 1.90 I got this linker error on CI:

Running unittests src/lib.rs (target/debug/deps/turso_sync_js-5f98d3f835f912a1)
/home/runner/_work/turso/turso/target/debug/deps/turso_sync_js-5f98d3f835f912a1: symbol lookup error: /home/runner/_work/turso/turso/target/debug/deps/turso_sync_js-5f98d3f835f912a1: undefined symbol: napi_typeof
error: test failed, to rerun pass `-p turso_sync_js --lib`

As David pointed out, the --warn-unresolved-symbols flag is enabled and the error only happens during runtime.

Using the old linker fix the issue. I do not know how to properly debug this so any help would be appreciated :)

Version it worked on

It most recently worked on: 1.88

Version with regression

rustc --version --verbose:

rustc 1.90.0 (1159e78c4 2025-09-14)
binary: rustc
commit-hash: 1159e78c4747b02ef996e55082b704c09b970588
commit-date: 2025-09-14
host: x86_64-unknown-linux-gnu
release: 1.90.0
LLVM version: 20.1.8

@rustbot modify labels: +regression-from-stable-to-stable -regression-untriaged

Start by reproducing the tursodb CI failure with Rust 1.88 and 1.90, focusing on the --warn-unresolved-symbols linker flag and the napi_typeof runtime error. Compare the behavior with the old linker and GNU LD; done means unresolved symbols are handled consistently and the regression is covered by a reproducible test.