Fix usage of github PR SHA in release job (#1041)

This was an oversight when refactoring the release workflow code last
week; it's not easy to test this step without creating spurious PRs on
the K repo so it got missed. It being missed produced a
[failure](https://github.com/runtimeverification/k/actions/runs/8943558614/job/24594103312?pr=4312)
in the LLVM backend update job.

The fix is to send the correct version information from the stashed
version file to the devops job, rather than the Git SHA as we were
previously doing.

---------

Co-authored-by: devops <[email protected]>

Author: Baltoli

.github/workflows/release.yml

@@ -92,11 +92,11 @@ jobs:
           GITHUB_TOKEN: ${{ secrets.JENKINS_GITHUB_PAT }}
         run: |
           set -x
-          version="${GITHUB_SHA}"
+          VERSION=$(cat package/version)
           curl --fail                                                          \
             -X POST                                                            \
             -H "Accept: application/vnd.github+json"                           \
             -H "Authorization: Bearer ${GITHUB_TOKEN}"                         \
             -H "X-GitHub-Api-Version: 2022-11-28"                              \
             https://api.github.com/repos/runtimeverification/devops/dispatches \
-            -d '{"event_type":"on-demand-test","client_payload":{"repo":"runtimeverification/llvm-backend","version":"'${version}'"}}'
+            -d '{"event_type":"on-demand-test","client_payload":{"repo":"runtimeverification/llvm-backend","version":"'${VERSION}'"}}'

package/debian/changelog

@@ -1,4 +1,4 @@
-k-llvm-backend (0.1.4) unstable; urgency=medium
+k-llvm-backend (0.1.5) unstable; urgency=medium
 
   * Initial release
 

package/version

@@ -1 +1 @@
-0.1.4
+0.1.5