fix: Use find instead of glob for Windows JAR exclusion compatibility

Windows bash (Git Bash/MSYS) doesn't expand globs the same way as Unix.
The pattern 'arcadedb-grpcw-*.jar' wasn't matching any files, resulting
in 0 JARs removed on Windows.

Change from:
  for jar in "$JARS_DIR"/$pattern; do
To:
  find "$JARS_DIR" -maxdepth 1 -name "$pattern" -type f

This uses find which is more portable across platforms and handles
Windows paths correctly.

Windows build log showed:
  Processing pattern: arcadedb-grpcw-*.jar
  ✅ Removed 0 JAR(s)
  ✅ Package prepared (84 JARs + JRE)

After fix, should show:
  Processing pattern: arcadedb-grpcw-*.jar
  - Removed: arcadedb-grpcw-25.10.1-SNAPSHOT-shaded.jar
  ✅ Removed 1 JAR(s)
  ✅ Package prepared (83 JARs + JRE)

Expected impact:
- Windows AMD64: 192.5M → ~157M (saves ~35M)

Author: tae898

bindings/python/build-native.sh

@@ -122,18 +122,14 @@ if [[ -f "$EXCLUSIONS_FILE" ]]; then
         # Skip empty lines and comments
         if [[ -n "$pattern" ]] && [[ ! "$pattern" =~ ^# ]]; then
             echo -e "${CYAN}   Processing pattern: $pattern${NC}"
-            # Remove matching JARs
-            shopt -s nullglob # Make glob expand to nothing if no matches
-            for jar in "$JARS_DIR"/$pattern; do
+            # Use find instead of glob for better cross-platform compatibility
+            while IFS= read -r jar; do
                 if [[ -f "$jar" ]]; then
                     rm -f "$jar"
                     echo -e "${YELLOW}   - Removed: $(basename "$jar")${NC}"
                     ((EXCLUSION_COUNT++))
-                else
-                    echo -e "${CYAN}   - Pattern matched but not a file: $jar${NC}"
                 fi
-            done
-            shopt -u nullglob
+            done < <(find "$JARS_DIR" -maxdepth 1 -name "$pattern" -type f 2> /dev/null)
         fi
     done < "$EXCLUSIONS_FILE"
     echo -e "${GREEN}✅ Removed $EXCLUSION_COUNT JAR(s)${NC}"