fix: publish stripped android aar

[ovitrif]

Refs synonymdev/bitkit-android#982

Related

• fix: retain native debug symbols bitkit-android#988
• fix: publish android debug symbols ldk-node#84
• fix: publish android debug symbols vss-rust-client-ffi#14
• fix: publish android dwarf symbols pubky/paykit-rs#54

Summary

• Publish stripped bitkit-core-android release AARs so app runtime artifacts do not carry .debug_* DWARF sections.
• Create native-debug-symbols.zip from unstripped Android libraries before stripping them.
• Publish that zip separately as the native-debug-symbols Maven classifier and as a release asset.
• Keep 16 KB LOAD alignment validation for both symbol sources and stripped release libraries.
• Keep the Gradle publish guard so the release AAR fails if packaged .so files contain .debug_* sections.

Published Artifacts

• Release: v0.1.73
• Workflow run: 27626818150
• Package: com.synonym:bitkit-core-android:0.1.73
• Symbol classifier: bitkit-core-android-0.1.73-native-debug-symbols.zip
• Release asset: native-debug-symbols.zip

QA Notes

• Passed locally: ./build_android.sh.
• Passed locally: actionlint .github/workflows/gradle-publish.yml.
• Passed locally: git diff --check.
• Remote package URLs return HTTP 200 for the POM, AAR, and native-debug-symbols classifier.
• Downloaded remote AAR is about 47 MB and contains no .debug_* sections in packaged libbitkitcore.so files.