[CI] simplify running end-to-end tests while building a release

.forgejo/cascading-release-end-to-end

@@ -9,4 +9,14 @@ forgejo_ref=$4
 
 cd $end_to_end
 date > last-upgrade
-echo $FORGEJO_BINARY > forgejo/binary-url
+organizations=lib/ORGANIZATIONS
+if ! test -f $organizations ; then
+    echo "$organizations file not found"
+    false
+fi
+#
+# do not include forgejo-experimental so that 7.0-test is found
+# in forgejo-integration where it was just built instead of
+# forgejo-experimental which was published by the previous build
+#
+echo forgejo forgejo-integration > $organizations

.forgejo/workflows/build-release.yml

@@ -203,11 +203,9 @@ jobs:
           destination-url: https://code.forgejo.org
           destination-fork-repo: ${{ vars.CASCADE_DESTINATION_DOER }}/end-to-end
           destination-repo: forgejo/end-to-end
-          destination-branch: forgejo-pr
+          destination-branch: main
           destination-token: ${{ secrets.CASCADE_DESTINATION_TOKEN }}
           update: .forgejo/cascading-release-end-to-end
-        env:
-          FORGEJO_BINARY: "${{ env.GITHUB_SERVER_URL }}/${{ github.repository }}/releases/download/v${{ steps.release-info.outputs.version }}/forgejo-${{ steps.release-info.outputs.version }}-linux-amd64"
 
       - name: copy to experimental
         if: vars.ROLE == 'forgejo-integration' && secrets.TOKEN != ''