Testing a71aecc483e4b9ea27b30b5944043f01de3dbc75

update README.md to verify apk builds

This just shares the same signing keystore with the CI. A better
solution would be a tool that verifies the contents of the apk are the
same, allowing you to compare apks that are signed by different keys.

Testing a68d642201cb32ad1f26bc5240e0b123c3a0aa7e

test_a68d642201cb32ad1f26bc5240e0b123c3a0aa7e

update android NDK version

Testing 66899a8523ec453847c94165bfab10bdbc97d689

test_66899a8523ec453847c94165bfab10bdbc97d689

Update README.md

Testing 5c1e91dce329354dc5da41ee51fff89d04168413

test_5c1e91dce329354dc5da41ee51fff89d04168413

Update Go Report Card

Testing 1663f2ec4023d074bfb5f249264ebf030294e186

test_1663f2ec4023d074bfb5f249264ebf030294e186

Test gogio with -trimpath and -buildid=

Testing 09f0fa6a17922fb74164c6f6d3ec10d464bbc9dc

test_09f0fa6a17922fb74164c6f6d3ec10d464bbc9dc

add keystore to verify apk is built reproducibly