android_sdk_repository isn't compatible with Bzlmod

[Bencodes]

The current Starlark implementation relies on native functions like bind and register_toolchains which are not supported in the Bzlmod MODULE.bazel file.

[keith]

this is mostly fixed by #147, for the bind uses we'll have to change bazel I believe

[meteorcloudy]

For avoiding bind usages, you can check https://bazel.build/external/migration#bind-targets, my guess is no Bazel change is required.

[meteorcloudy]

Oh, unless some Bazel native code is referring to //external:*.. /cc @ahumesky @ted-xie

[katre]

Native Android rules depend on //external for a variety of things (mostly implicit dependencies on tools and the SDKs).

We should be able to remove these in the Starlark rules for the most part.

[meteorcloudy]

Probably here: https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/bazel/rules/android/AndroidSdkRepositoryRule.java;l=38-45

[meteorcloudy]

And https://cs.opensource.google/bazel/bazel/+/master:src/tools/android/java/com/google/devtools/build/android/r8/BUILD;l=55

I believe even before starlarkfying the android build rules, we can just replace those labels to directly pointing to @bazel_tools

[katre]

The actual labels are in @androidsdk, unless the user names the repo something different, and not all projects even create the repo (which is why //external:has_androidsdk exists).