[ Bazel ci] Error name 'aar_import' is not defined with Bazel@HEAD

[sgowroji]

CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3858#018f7a6e-1950-49f1-9151-af3cc2389a2e

Platform: Ubuntu

Logs:

ERROR: �[0m/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/d15077c341827e73bf2d88b7f622d6f3/external/maven/BUILD:9:1: name 'aar_import' is not defined (did you mean 'cc_import'?)

Culprit: bazelbuild/bazel@947c72d

Steps:

git clone https://github.com/bazelbuild/rules_kotlin
git reset 42ea2e5539ec52ef93cf29607aa889b7d57ea320  --hard
export USE_BAZEL_VERSION=88a230f4cf28deec1455cb2caed4dc9f81e108c9
bazel test  //app:all 

CC Greenteam @fweikert

[sgowroji]

CC @ahumesky @ted-xie

[restingbull]

Should be fixed by bazel-contrib/rules_jvm_external#1149

[ahumesky]

bazel-contrib/rules_jvm_external#1149 was just merged

[ahumesky]

Note that bazel-contrib/rules_jvm_external#1149 was reverted: bazel-contrib/rules_jvm_external#1215 due to accidentally requiring all projects that use rules_jvm_external to use --experimental_google_legacy_api. rules_kotlin might already be using --experimental_google_legacy_api so it might be acceptable to use a version of rules_jvm_external before the revert, but of course then you're stuck with that version until the issue with --experimental_google_legacy_api is resolved.