Initial Android support

[enfipy]

Closes #87

I was able to run shaderc-rs on the Android app with dynamically linked shaderc that was built with the ndk-build tool inside build/shaderc/android_test folder with the following command:

ndk-build APP_BUILD_SCRIPT=Android.mk SPVTOOLS_LOCAL_PATH=../third_party/spirv-tools SPVHEADERS_LOCAL_PATH=../third_party/spirv-headers APP_STL:=c++_shared APP_ABI=all -j

Then I provide the path to the libs folder as SHADERC_LIB_DIR. I'm sure that this is not a good way to make it work but still - it works and I want to hear any feedback on how to make it right.

Also, there's still not possible to build it with the CARGO_FEATURE_BUILD_FROM_SOURCE and without PITA while building it with ndk-build by yourself. Should I add ndk-build to build.rs or there some way to do it with ninja?

[google-cla[bot]]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

:memo: Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

:memo: Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[antiagainst]

Thanks for adding this!! Could you rebase first? The buildbots failure is fixed at top of the tree. I'll take a look later. :)