ci: resolve commitlint and release job failures

[charlesmulder]

Description

Fixes two CI failures from commits 558f7b6 and 9aca923:

1. Commitlint body-max-line-length failure — Dependabot commits contain long URLs and metadata in body (>100 chars). Disabled the rule in commitlint.config.js since URLs, co-author lines, and bot metadata routinely exceed this limit.

2. Release job race condition — When commits land on main simultaneously, release jobs can overlap and fail with non-fast-forward push errors. Added concurrency group to serialize release jobs.

No JIRA ticket (CI maintenance).

---

How to test locally

Commitlint fix:

# Test that long body lines now pass
echo "chore(deps-dev): bump qs

$(python3 -c "print('x' * 150)")" | npx commitlint
# Should pass with no errors

# Run commitlint tests
npx jest --config=commitlint.jest.config.js

Concurrency group:

• Verify in GitHub Actions UI — concurrent release jobs will queue instead of running in parallel
• Check this PR's CI passes without commitlint errors

---

Anything reviewers should know?

• body-max-line-length is low-value lint for commit messages (only enforces style, not correctness)
• Concurrency group serializes release jobs with FIFO queue, cancel-in-progress: false prevents canceling in-flight releases
• Concurrency group scoped to this workflow only (CI-release)

---

Checklist

• Tests: new/updated tests cover the change
• API: spec updated if endpoints changed (or N/A)
• Migrations: backwards compatible if schema changed (or N/A)
• Dependencies: no known impact to dependent services
• Security: reviewed against secure coding checklist (or N/A)

AI disclosure

Assisted by: Claude Code