Fix Android SDK path detection in CI container environment

Updated `AndroidGradleBuilder.java` to improve SDK path detection. Instead of assuming any `ANDROID_HOME` path that doesn't end in "sdk" must be a parent directory, the builder now validates the directory content (checking for `platform-tools`, `build-tools`, etc.) before modifying the path. This change ensures compatibility with the new CI container layout where `ANDROID_HOME` points directly to the SDK root at `/opt/android-sdk` (or `/opt/android/sdk`) without forcing an incorrect `/sdk` suffix.

Author: google-labs-jules[bot]

maven/codenameone-maven-plugin/src/main/java/com/codename1/builders/AndroidGradleBuilder.java

@@ -577,7 +577,13 @@ public boolean build(File sourceZip, final BuildRequest request) throws BuildExc
         if (!androidSDKDir.exists()) {
             throw new BuildException("Cannot find Android SDK at "+androidHome+".  Please install Android studio, or set the ANDROID_HOME environment variable to point to your android sdk directory.");
         }
-        if (!androidSDKDir.getName().equalsIgnoreCase("sdk")) {
+
+        boolean looksLikeSdk = new File(androidSDKDir, "platform-tools").exists() ||
+                               new File(androidSDKDir, "build-tools").exists() ||
+                               new File(androidSDKDir, "cmdline-tools").exists() ||
+                               new File(androidSDKDir, "platforms").exists();
+
+        if (!looksLikeSdk && !androidSDKDir.getName().equalsIgnoreCase("sdk")) {
             androidSDKDir = new File(androidSDKDir, "Sdk");
             if (!androidSDKDir.isDirectory()) {
                 androidSDKDir = new File(androidSDKDir.getParentFile(), "sdk");