fix: copy local meta.yaml in release workflow for bioconda PR

The release workflow was only sed-patching version/sha256 into whatever
meta.yaml existed upstream in bioconda-recipes. Structural changes (deps,
build flags) from our local recipes/smaca/meta.yaml were never propagated,
causing py313 builds to fail (missing setuptools).

Now the workflow checks out this repo and copies our local meta.yaml
before applying version/sha256/build-number substitutions.

Author: dlopez-bioinfo

.github/workflows/release.yml

@@ -103,6 +103,11 @@ jobs:
           GH_TOKEN: ${{ secrets.GH_PAT }}
         run: gh repo sync ${FORK_USER}/bioconda-recipes --source bioconda/bioconda-recipes --branch master
 
+      - name: Checkout SMAca repo
+        uses: actions/checkout@v4
+        with:
+          path: smaca-repo
+
       - name: Checkout fork of bioconda-recipes
         uses: actions/checkout@v4
         with:
@@ -113,6 +118,7 @@ jobs:
       - name: Update recipe
         working-directory: bioconda-recipes
         run: |
+          cp ../smaca-repo/recipes/smaca/meta.yaml recipes/smaca/meta.yaml
           sed -i "s/^{% set version = .* %}/{% set version = \"${VERSION}\" %}/" recipes/smaca/meta.yaml
           sed -i "s/sha256: .*/sha256: ${SHA256}/" recipes/smaca/meta.yaml
           sed -i "s/^  number: .*/  number: 0/" recipes/smaca/meta.yaml