fix: add Android ELF build IDs

[ovitrif]

Summary

Add -Wl,--build-id=sha1 to the Android linker configuration for every published bitkit-core ABI. Google Play uses ELF build IDs to match packaged native libraries with uploaded debug symbols.

Deliverables

• Preserve the existing linker and 16 KB page-size flags.
• Bump the cross-platform package version.
• Refresh the tracked mobile release artifacts.
• Publish the versioned Android artifact and its existing native debug-symbol archive.

Acceptance criteria

• The Android linker configuration includes -Wl,--build-id=sha1 for armeabi-v7a, arm64-v8a, x86, and x86_64.
• The repository's ordinary build, test, and lint checks pass.
• The versioned Android artifact is published.
• Bitkit Android adopts the released artifact.

Coordination

• Epic: epic: add Android ELF build IDs bitkit-android#1105
• Implementation: fix: add android elf build ids #131

[ovitrif]

The implementation is ready for review in #131.

The PR publishes 0.4.4, validates all four Android ABIs, preserves SHA-1 GNU build IDs through stripping, requires full DWARF symbols, and gates Maven publication on final AAR-to-symbol parity. Its locally published artifacts were consumed successfully by the integrated Bitkit Android release build.

Remaining follow-up: exact-head approval, merge, versioned release publication, and released-artifact verification in synonymdev/bitkit-android#1106. This issue remains open through that release gate.

[ovitrif]

Scope correction: this issue remains open under the separate Android ELF build-ID epic synonymdev/bitkit-android#1105. bitkit-core’s missing GNU build IDs prevent Google Play from pairing its packaged library with uploaded debug symbols; adding them enables native symbolication. This work is independent of the DataStore-only resolution of synonymdev/bitkit-android#1047.