🔧 Fix ARM64 cross-compilation with OpenSSL static linking

Resolve OpenSSL cross-compilation issues for ARM64 Linux builds

- Add --no-install-recommends flag to apt-get install for cleaner
  dependency management
- Set OPENSSL_STATIC=1 to force static linking of OpenSSL
- Set OPENSSL_VENDOR=1 to use vendored OpenSSL for cross-compilation
- Add descriptive comments explaining ARM64 setup steps

This change eliminates OpenSSL cross-compilation complexity that was
causing ARM64 build failures by forcing the use of vendored OpenSSL
instead of system libraries.

Author: hyperb1iss

.github/workflows/cicd.yml

@@ -185,9 +185,13 @@ jobs:
         if: matrix.target == 'aarch64-unknown-linux-gnu'
         run: |
           sudo apt-get update
-          sudo apt-get install -y gcc-aarch64-linux-gnu
+          # Install cross-compiler for ARM64
+          sudo apt-get install -y --no-install-recommends gcc-aarch64-linux-gnu
           echo "CC_aarch64_unknown_linux_gnu=aarch64-linux-gnu-gcc" >> $GITHUB_ENV
           echo "CARGO_TARGET_AARCH64_UNKNOWN_LINUX_GNU_LINKER=aarch64-linux-gnu-gcc" >> $GITHUB_ENV
+          # Use vendored OpenSSL to avoid cross-compilation complexity
+          echo "OPENSSL_STATIC=1" >> $GITHUB_ENV
+          echo "OPENSSL_VENDOR=1" >> $GITHUB_ENV
 
       - name: 📦 Rust cache
         uses: Swatinem/rust-cache@v2