chore(deps): bump devantler-tech/.github/actions/upsert-issue (#324)

Bumps [devantler-tech/.github/actions/upsert-issue](https://github.com/devantler-tech/.github) from 2.2.2 to 2.5.1.
- [Release notes](https://github.com/devantler-tech/.github/releases)
- [Commits](8dc4224...37da047)

---
updated-dependencies:
- dependency-name: devantler-tech/.github/actions/upsert-issue
  dependency-version: 2.5.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Author: dependabot[bot]

.github/workflows/repository-coverage-check.yaml

@@ -81,7 +81,7 @@ jobs:
     steps:
       - name: 📣 Open or update the tracking issue
         if: needs.repository-coverage-check.result != 'success'
-        uses: devantler-tech/.github/actions/upsert-issue@8dc42244b1ef88a9091bd5cf907258471eef6f46 # v2.2.2
+        uses: devantler-tech/.github/actions/upsert-issue@37da04790ccaeef0ff890de572b0903a079d3f6f # v2.5.1
         with:
           title: "Scheduled repository coverage check is failing on main"
           body: |
@@ -93,7 +93,7 @@ jobs:
             Read the failing step first. A failure at `🔑 Get GitHub App Token` means the App credential needs attention. An `UNDECLARED` line names a live repository that `deploy/` does not declare: adopt it in `deploy/` (Observe-first), never by changing the live repository. A `STALE-EXEMPTION` line names an exemption in `scripts/check-repository-coverage.sh` to remove, and an `UNSEEN` line means the listing could not see the whole org. This issue is updated by every failing run and closed by the next passing one.
       - name: ✅ Close the tracking issue
         if: needs.repository-coverage-check.result == 'success'
-        uses: devantler-tech/.github/actions/upsert-issue@8dc42244b1ef88a9091bd5cf907258471eef6f46 # v2.2.2
+        uses: devantler-tech/.github/actions/upsert-issue@37da04790ccaeef0ff890de572b0903a079d3f6f # v2.5.1
         with:
           title: "Scheduled repository coverage check is failing on main"
           open: "false"

.github/workflows/repository-drift-check.yaml

@@ -106,7 +106,7 @@ jobs:
     steps:
       - name: 📣 Open or update the tracking issue
         if: needs.repository-drift-check.result != 'success'
-        uses: devantler-tech/.github/actions/upsert-issue@8dc42244b1ef88a9091bd5cf907258471eef6f46 # v2.2.2
+        uses: devantler-tech/.github/actions/upsert-issue@37da04790ccaeef0ff890de572b0903a079d3f6f # v2.5.1
         with:
           title: "Scheduled repository drift check is failing on main"
           body: |
@@ -118,7 +118,7 @@ jobs:
             Read the failing step first. A failure at `🔑 Get GitHub App Token` means the App credential needs attention. A `DRIFT` line from the compare step means a declared repository setting never reached the live repository: fix the resource in `deploy/`, never the live repository. This issue is updated by every failing run and closed by the next passing one.
       - name: ✅ Close the tracking issue
         if: needs.repository-drift-check.result == 'success'
-        uses: devantler-tech/.github/actions/upsert-issue@8dc42244b1ef88a9091bd5cf907258471eef6f46 # v2.2.2
+        uses: devantler-tech/.github/actions/upsert-issue@37da04790ccaeef0ff890de572b0903a079d3f6f # v2.5.1
         with:
           title: "Scheduled repository drift check is failing on main"
           open: "false"