Fix: Compatibility with different versions of 'Stability' in Android Binder Protocol

[tsailin-bit]

panic on Android 12

OnePlus8T:/data/local/tmp # ./hello_service
[2024-03-11T13:37:55Z WARN  rsbinder::process_state] Binder ioctl to enable oneway spam detection failed: EINVAL: Invalid argument
[2024-03-11T13:37:55Z WARN  rsbinder::thread_state] binder::BR_REPLY (BadType)
Error: TransactionFailed / BadType:

Android 12 version uses "Category" as the stability format for passed on the wire lines, whereas other versions do not. Therefore, we can use the android_properties crate to determine the Android version and perform different handling accordingly.
http://aospxref.com/android-11.0.0_r21/xref/frameworks/native/libs/binder/include/binder/Stability.h
http://aospxref.com/android-12.0.0_r3/xref/frameworks/native/include/binder/Stability.h
http://aospxref.com/android-13.0.0_r3/xref/frameworks/native/libs/binder/include/binder/Stability.h
http://aospxref.com/android-14.0.0_r2/xref/frameworks/native/libs/binder/include/binder/Stability.h

[hiking90]

When I tested it, changing only the stability value as you suggested didn't cause any problems on Android 12 and 13. If it's stated that it only supports Android 12 and above, this should be sufficient. Can you rewrite the patch with the following content? I ask because I want to keep a record of your contribution.

Vendor => 0x0c000003,
System => 0x0c00000c,
Vintf => 0x0c00003f,

[hiking90]

I merged your PR.
Then I added another commit that removes the dependency on android-properties and changes it so that developers can specify the Android version through the set_android_version() function. This was because android-properties was not built in the NDK environment.