Flag --incompatible_no_implicit_file_export will break Bazel toolchains 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 Bazel toolchains.

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

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

* RBE (Ubuntu 16.04, OpenJDK 8)
* RBE (Ubuntu 16.04, OpenJDK 8)

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 Bazel toolchains 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.

Start with the two linked Buildkite CI runs and the linked Bazel incompatible-flags documentation. Inspect the Bazel toolchain configurations exercised by those builds and determine what fails when --incompatible_no_implicit_file_export is enabled; done means the affected builds and tests pass with the flag.

Written by the indexing model from the issue text.