Flag --incompatible_no_implicit_file_export will break Android Testing in a future Bazel release

Incompatible flag --incompatible_no_implicit_file_export will be enabled by default in a future Bazel release [1], thus breaking Android Testing.

The flag is documented here: https://github.com/bazelbuild/bazel/issues/10225

Please check the following CI builds for build and test results:

* Ubuntu 16.04, OpenJDK 8
* Windows, OpenJDK 8
* macOS, OpenJDK 8
* Ubuntu 18.04, OpenJDK 11

Never heard of incompatible flags before? We have [documentation](https://docs.bazel.build/versions/master/backward-compatibility.html) that explains everything.

If you don't want to receive any future issues for Android Testing or if you have any questions,
please file an issue in https://github.com/bazelbuild/continuous-integration

**Important**: Please do NOT modify the issue title since that might break our tools.

[1] The target release hasn't been determined yet. Our tool will update the issue title once the flag flip has been scheduled.

まず、リンクされているBazelの非互換フラグに関するドキュメントと、Android Testingの4件のBuildkite CI結果を確認してください。--incompatible_no_implicit_file_exportが原因で発生したAndroid Testingのビルドまたはテストの失敗を特定し、その後、将来このフラグのデフォルトが切り替わる前に、一覧にあるすべてのプラットフォームがフラグを有効にした状態でパスすることを確認してください。

索引モデルが issue の本文から書いたものです。