Native upload without --force: FULL symbols never replace earlier SYMBOL_TABLE ones for the same build-id #9

Summary

The native upload runs bugsee-cli debug-files upload --type elf without --force. When the server already holds symbols for a build-id, the CLI skips the file. If an app first uploaded SYMBOL_TABLE symbols (function names only) and later switches to FULL (DWARF, file:line), prebuilt libraries whose build-id doesn't change between app releases — e.g. React Native's libreactnative.so from Maven, which keeps its build-id until React Native is upgraded — never get their FULL symbols uploaded, so native crashes in them keep showing function names only.

Expected

A richer symbol file for the same build-id replaces a poorer one: either the CLI/server treat FULL (.so.dbg) as superseding SYMBOL_TABLE (.so.sym) for the same build-id, or the plugin passes --force (or an equivalent "upgrade if richer" flag) for native uploads.

Context

The React Native wrapper's Expo config plugin now defaults to debugSymbolLevel 'FULL' (bugsee/bugsee-react-native#64); apps upgrading from an earlier prebuild that wrote SYMBOL_TABLE will hit this. To be confirmed on staging by the RN campaign's STAGING lane; this issue records the expected behaviour.