chore: standardize/update release please config

[toddbaert]

Standardizes this repo's release-please setup. Part of open-feature/community-tooling#128.

• pin googleapis/release-please-action@45996ed…307cf7 # v5
• token: ${{ secrets.RELEASE_PLEASE_ACTION_TOKEN }}
• signoff configured in release-please-config.json (removes deprecated command/default-branch/signoff inputs); fixes DCO on release PRs
• release gate uses the always-emitted, monorepo-safe plural releases_created via fromJSON(... || false)
• add a concurrency guard to serialize release-please runs

Single signed-off commit; no changes to custom publish/build steps.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: df5a3191-294c-453f-b8be-95b367d886c2

📥 Commits

Reviewing files that changed from the base of the PR and between c3fedd3 and ddbcdc0.

📒 Files selected for processing (1)

• .github/workflows/release.yml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The release workflow now groups runs by github.ref without cancelling in-progress runs. It also upgrades the release-please action to v5 and uses RELEASE_PLEASE_ACTION_TOKEN.

Changes

Release workflow

Layer / File(s)	Summary
Release-please workflow configuration .github/workflows/release.yml	The workflow groups runs by github.ref and sets cancel-in-progress to false. It upgrades googleapis/release-please-action to v5 and changes its token input to RELEASE_PLEASE_ACTION_TOKEN.

Estimated code review effort: 2 (Simple) | ~8 minutes

Suggested reviewers: gruebel

Merge Risk: ⚪ Minimal · up to ddbcd

The release workflow changes are mergeable with normal checks; no concrete release-blocking issue is established.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: standardizing and updating the Release Please configuration.
Description check	✅ Passed	The description directly explains the Release Please updates, token change, signoff configuration, release gate, concurrency guard, and unchanged publish steps.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

_{Comment @coderabbitai help to get the list of available commands.}