Separate Sanitizers for Android

[TheCoryBarker]

This is to create a separate list of Android sanitizers. These sanitizers will be packaged up with the rest of the sanitizers for a normal Jazzer build, and then the user can specify to use these sanitizers at instrumentation time with the flag --use_android_sanitizers. This flag will be used for Android for offline instrumentation, like so:

> ./jazzer --instrument_only=<fuzz_target>.jar --dump_classes_dir=/tmp --use_android_sanitizers

and then you'll have a jar file that is instrumented for Android. The Jazzer built for Android wont need all of the sanitizers, so only the Android sanitizers will be included in the Android build.

The reasons to keep these lists separate are:

• Some sanitizers will cause crashes on Android if used on Android code (RegexInjection.java) so we want to make sure these are excluded for all Android runs. There may be more in the future that are added that need to not be added to Android
• ALthough the one sanitizer I added specific for Android (converted SQL Injection sanitizer) wont cause any issues for a normal JVM if it is used at runtime, it is possible a future one will cause issues, so it's best to just keep them on a separate list of sanitizers

[TheCoryBarker]

Could we instead get by with select on @platforms//os:android and, if necessary, a bool_flag?

We already have more runtime flags than we should, which makes testing more difficult.

I like this idea, I'll make this change