CI on dev shows failing Dependabot Updates runs (x/crypto security update)

[rogeralsing]

Default branch CI is failing.

Combined status: pending
Latest workflow run: completed / failure
Run URL: https://github.com/asynkron/protoactor-go/actions/runs/21072165206

Latest status checks:

[rogeralsing]

Investigated failing runs on dev: GitHub Actions workflow path dynamic/dependabot/dependabot-updates fails with pull_request_exists_for_security_update for golang.org/x/crypto@0.45.0 (example run: https://github.com/asynkron/protoactor-go/actions/runs/21072165206).

Proposed fix is in PR #1278: #1278

It bumps golang.org/x/crypto to v0.45.0 in the root module + examples/cluster-eventstream-broadcast so the security update job should no longer trigger/fail once merged.

[rogeralsing]

Root cause: built-in "Dependabot Updates" runs on are failing with because a security PR already exists for (e.g. #1270 / #1269).\n\nFix: #1278 bumps to (root module + ) so the security update becomes a no-op and the Dependabot Updates workflow stops failing.\n\nRepro detail: failing run https://github.com/asynkron/protoactor-go/actions/runs/21072165206 ends with "Pull request already exists for golang.org/x/crypto@0.45.0".

[rogeralsing]

Follow-up (previous comment got shell-escaped):

Root cause: built-in "Dependabot Updates" runs on branch "dev" fail with "pull_request_exists_for_security_update" because a security PR already exists for "golang.org/x/crypto@0.45.0" (#1269 root module, #1270 examples/cluster-eventstream-broadcast).

Fix: PR #1278 bumps golang.org/x/crypto to v0.45.0 in both modules so the security update becomes a no-op and the Dependabot Updates workflow stops failing.

Reference failing run: https://github.com/asynkron/protoactor-go/actions/runs/21072165206