ci(release): Use container in workflow instead of build-in-docker.sh

This eases maintainability, as the workflow is direcltly defined in `build.yml`. This will also allow us to add caching of dependencies more easily, and make the workflow for Linux more closely match the workflow for macOS and Windows.

Author: szokeasaurusrex

.github/workflows/build.yml

@@ -27,17 +27,17 @@ jobs:
     name: Linux ${{ matrix.arch }}
     runs-on: ubuntu-24.04
 
+    container:
+      image: messense/rust-musl-cross:${{ matrix.container }}
+
     steps:
       - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # 5.0.0
 
-      - name: Build in Docker
-        run: scripts/build-in-docker.sh
-        env:
-          TARGET: ${{ matrix.target }}
-          DOCKER_TAG: ${{ matrix.container }}
+      - name: Build
+        run: cargo build --release --target=${{ matrix.target }} --locked
 
       - name: Rename Binary
-        run: mv target/*/release/sentry-cli sentry-cli-Linux-${{ matrix.arch }}
+        run: mv target/${{ matrix.target }}/release/sentry-cli sentry-cli-Linux-${{ matrix.arch }}
 
       - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # 4.6.2
         with: