fix(ci): gate release and package-deletion jobs behind release environment (#222)

Both the release job and the delete-packages-and-releases job could run
without any approval gate, even though the destructive delete workflow is
directly dispatchable and is also invoked by release.yml. Adding
`environment: release` to each job routes them through the existing
`release` GitHub Environment, which already has required reviewers and a
branch policy configured.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: cx-lior-poterman

.github/workflows/delete-packages-and-releases.yml

@@ -23,6 +23,7 @@ permissions:
 jobs:
   delete:
     name: Delete packages and releases
+    environment: release
     permissions:
       contents: write  # for gh release delete and tag cleanup
       packages: write  # for deleting npm package versions

.github/workflows/release.yml

@@ -63,6 +63,7 @@ jobs:
     if: inputs.dev == true
   release:
     name: Release
+    environment: release
     permissions:
       id-token: write  # allows this job to request a GitHub OIDC token
       contents: write  # for git tag push and creating the GitHub release