Android CHIP demo app

[vidhis88]

Scan CHIP QR code and display the SetupPayload info.

Video: https://drive.google.com/file/d/1BqqjPsQItrdNCNtfjfR5W4zMKUVkiTpy/view

[pan-apple]

Are the following files build artifacts being accidentally checked in?

src/android/CHIPTool/app/src/main/jniLibs/arm64-v8a/libcrypto.so
src/android/CHIPTool/app/src/main/jniLibs/arm64-v8a/libSetupPayloadParser.so
src/android/CHIPTool/app/src/main/jniLibs/x86/libSetupPayloadParser.so
src/android/CHIPTool/app/src/main/jniLibs/x86/libcrypto.so

[andy31415]

Are the following files build artifacts being accidentally checked in?

src/android/CHIPTool/app/src/main/jniLibs/arm64-v8a/libcrypto.so
src/android/CHIPTool/app/src/main/jniLibs/arm64-v8a/libSetupPayloadParser.so
src/android/CHIPTool/app/src/main/jniLibs/x86/libSetupPayloadParser.so
src/android/CHIPTool/app/src/main/jniLibs/x86/libcrypto.so

Maybe we could use some $NDK_PATH in our build scripts for the crypto bit. For the PayloadParser, it sounds as if our build should create that file and we should not need to check it in.

[andy31415]

Marking as changes requested: I believe we should not checkin .so files and we should instead require user paths if we cannot autodetect (e.g. chip build output directory or NDK path).

[gerickson]

Looks good, but agreed we do not want to check in the .so binaries.

[randyrossi]

Same goes for .jar files. Any artifacts of the build should not be checked in.

[woody-apple]

@vidhis88 @randyrossi any update here?

[vidhis88]

Updated the PR to remove the .so and .jar files.

Since we don't yet have a build job for the Android app, I wanted to allow anyone checking out the Android demo app to be able to run it without having to manually build the .so and .jar files by including them.
But I do see the point of muddying git history and have updated the PR accordingly.