Fix Android workflow binary extraction with robust approach

- Add tar -tzf to list contents before extraction
- Add ls -la to show extracted files
- Use find with wildcard pattern to locate any xfg-stark-cli binary
- Use variable to store found binary path
- This should handle any directory structure in the tar.gz file
- More robust than assuming specific file names

Author: ColinRitman

.github/workflows/android-release.yml

@@ -65,11 +65,15 @@ jobs:
       - name: Download xfg-stark-cli
         run: |
           curl -L -o xfg-stark-cli-linux.tar.gz "https://github.com/ColinRitman/xfgwin/releases/download/v0.8.8/xfg-stark-cli-linux.tar.gz"
-          tar -xzf xfg-stark-cli-linux.tar.gz --strip-components=1
-          find . -name "xfg-stark-cli-linux" -type f
-          chmod +x xfg-stark-cli-linux
+          tar -tzf xfg-stark-cli-linux.tar.gz
+          tar -xzf xfg-stark-cli-linux.tar.gz
+          ls -la
+          find . -name "*xfg-stark-cli*" -type f
+          BINARY_PATH=$(find . -name "*xfg-stark-cli*" -type f | head -1)
+          echo "Found binary at: $BINARY_PATH"
+          chmod +x "$BINARY_PATH"
           mkdir -p assets/bin
-          mv xfg-stark-cli-linux assets/bin/
+          mv "$BINARY_PATH" assets/bin/xfg-stark-cli-linux
           rm xfg-stark-cli-linux.tar.gz
 
       - name: Download fuego-walletd