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.

Commencez par examiner la documentation Bazel liée sur les flags incompatibles ainsi que les quatre résultats de Buildkite CI pour Android Testing. Identifiez les échecs de build ou de test d’Android Testing causés par --incompatible_no_implicit_file_export, puis vérifiez que toutes les plateformes répertoriées réussissent avec le flag activé avant son futur changement de valeur par défaut.

Rédigé par le modèle d'indexation à partir du texte de l'issue.