Build failure on head/rolling Bazel

Example: https://buildkite.com/bazel/rules-android-ndk/builds/362/list?sid=019fa9f1-4397-4235-abf2-36998e391693&tab=output

```
(04:01:14) ERROR: /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/9d5739ab914109ed76e2d2bc404eb2d4/external/rules_android+/rules/android_split_transition.bzl:116:38: transition inputs [//command_line_option:android_compiler] do not correspond to valid settings
--
  | (04:01:14) ERROR: /workdir/examples/basic/java/com/app/BUILD:4:15: on dependency edge //java/com/app:app (7e0cc4f) -\|deps\|-> //java/com/app:applib: Errors encountered while applying Starlark transition
  | (04:01:14) ERROR: Analysis of target '//java/com/app:app' failed; build aborted
```

Likely due to https://github.com/bazelbuild/bazel/commit/d38b15061ac51e549cc30c82341877f636150536

cc @aranguyen

Reproduce the failure from the Buildkite example, then inspect rules/android_split_transition.bzl at line 116 and compare the behavior with the referenced Bazel commit. Done means the examples/basic/java/com/app build succeeds on head/rolling Bazel without the invalid android_compiler transition error.

Written by the indexing model from the issue text.