fix: resolve cibuildwheel and BoringSSL build issues

- Upgrade cibuildwheel from v2.16.2 to v2.22.0 to fix Windows PowerShell parameter escaping
- Add -Wno-maybe-uninitialized flags to BoringSSL build to fix GCC false positive warning
- Refactor release workflow to use reusable _test.yml workflow
- Add config job for test enable/disable control

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: arman-bd

.github/workflows/release.yml

@@ -50,10 +50,7 @@ jobs:
         submodules: recursive
 
     - name: Build wheels
-      uses: pypa/cibuildwheel@v2.16.2
-      with:
-        package-dir: .
-        output-dir: wheelhouse
+      uses: pypa/cibuildwheel@v2.22.0
 
     - uses: actions/upload-artifact@v4
       with:

scripts/setup_vendors.sh

@@ -84,8 +84,14 @@ if [ ! -f "$SSL_LIB_FILE" ]; then
               ..
         cmake --build . --config Release
     else
+        # Disable maybe-uninitialized warning for BoringSSL (false positive in GCC)
+        export CFLAGS="${CFLAGS:-} -Wno-maybe-uninitialized"
+        export CXXFLAGS="${CXXFLAGS:-} -Wno-maybe-uninitialized"
+
         cmake -DCMAKE_BUILD_TYPE=Release \
               -DCMAKE_POSITION_INDEPENDENT_CODE=ON \
+              -DCMAKE_C_FLAGS="-Wno-maybe-uninitialized" \
+              -DCMAKE_CXX_FLAGS="-Wno-maybe-uninitialized" \
               ..
         make -j$(nproc 2>/dev/null || sysctl -n hw.ncpu 2>/dev/null || echo 4)
     fi