Add concurrency control to 23 GitHub Actions workflows

## Recommendation

### ⚙️ Add Concurrency Groups

23 workflows lack `concurrency:` configuration. Without it, multiple runs of the same workflow on the same branch stack up instead of canceling outdated ones, wasting CI minutes.

## Affected Workflows

api-update-electron-api-types, api-update-manager-api-types, api-update-registry-api-types, ci-json-validation, ci-python-validation, ci-shell-validation, ci-tests-e2e-forks, ci-tests-storybook-forks, ci-tests-storybook, ci-validate-action-pins, ci-yaml-validation, cloud-backport-tag, cloud-dispatch-cleanup, i18n-update-core, i18n-update-custom-nodes, i18n-update-nodes, pr-request-team-review, publish-desktop-ui-on-merge, release-biweekly-comfyui, release-branch-create, release-draft-create, release-pypi-dev, version-bump-desktop-ui

## How to Fix

Add to each applicable workflow:
```yaml
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
```

Note: For release/publish workflows, use `cancel-in-progress: false` to avoid interrupting deployments.

---
**Category:** CI/CD Efficiency | **Priority:** Recommended | **Effort:** Trivial
Part of #11022
_Filed by repo-audit skill_

┆Issue is synchronized with this [Notion page](https://www.notion.so/Issue-11027-Add-concurrency-control-to-23-GitHub-Actions-workflows-33e6d73d365081c38d97e6ef99694ecf) by [Unito](https://www.unito.io)