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 不兼容 flag 文档以及 Android Testing 的四个 Buildkite CI 结果。识别由 --incompatible_no_implicit_file_export 导致的 Android Testing 构建或测试失败，然后在该 flag 启用的情况下验证所有列出的平台均能通过，再等待其未来默认值切换。

由索引模型根据 Issue 内容生成。