fix: pin truenas-proxmox-multipath to the exact base package version (#299)

TrueNASMultipath.pm calls the base plugin's private helpers, and from 4.0.2
it also calls SUPER::volume_resize. So it only works with the truenas-proxmox
built from the same commit. `>= 3.1.0` let apt pair 4.0.2 multipath with
a 3.2.5 or 4.0.1 base, which fails at runtime. `(= ${VERSION})` makes apt
upgrade or hold the two together. A CI check fails the build if the
template ever drifts.

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

.github/workflows/build.yml

@@ -272,6 +272,14 @@ jobs:
           echo "==> Package info (truenas-proxmox-multipath):"
           dpkg-deb --info "${{ steps.vars.outputs.multipath_deb_file }}"
 
+          # Multipath calls the base plugin's private helpers and SUPER:: methods,
+          # so it must be pinned to the exact base version built alongside it (#299).
+          VERSION="${{ steps.vars.outputs.version }}"
+          DEPENDS="$(dpkg-deb -f "${{ steps.vars.outputs.multipath_deb_file }}" Depends)"
+          echo "==> multipath Depends: ${DEPENDS}"
+          echo "${DEPENDS}" | grep -qF "truenas-proxmox (= ${VERSION})" \
+            || { echo "::error::multipath must depend on truenas-proxmox (= ${VERSION})"; exit 1; }
+
       - name: Upload package artifacts
         uses: actions/upload-artifact@v4
         with: