ci: fix brittle docs-theme publish workflow

[Copilot]

• Add concurrency group to queue concurrent workflow runs
• Read latest version from npm before bumping, with fallback to local package.json
• Make commit step best-effort (continue-on-error: true)
• Replace stefanzweifel/git-auto-commit-action with EndBug/add-and-commit@v9 for consistency with other workflows

Original prompt

---

This section details on the original issue you should resolve

<issue_title>apify-docs-theme CI publish is brittle</issue_title>
<issue_description>The multistep docs-theme publishing setup reads the current version number from the repository, bumps it, and then tries to publish. If the publish succeeds, the new version number is then committed to the repository.

This approach is error-prone as the version number read and write (commit) are not atomic. Another commit to master can happen in the meantime and can overwrite the version number (causing the git commit to fail). Once the git-tracked version number is out of sync w/ npm, the entire workflow breaks.</issue_description>

<agent_instructions>Solve the described issue. Try removing the need for committing the package version to the repository - maybe read the latest version from npm directly before bumping? Also, add exclusive concurrency groups to the theme publishing action. Still commit the version to the repository (best effort basis?), though.

Make minimal changes to achieve this. Use conventional commits for the commit message and PR titles. Do not add excessive comments.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes apify-docs-theme CI publish is brittle #2302

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

---

Note

^{Cursor Bugbot is generating a summary for commit 9bc28e7. Configure here.}

[apify-service-account]

Preview for this PR was built for commit 9bc28e7 and is ready at https://pr-2303.preview.docs.apify.com!

[barjin]

lgtm (mostly because I prompted this), now I need the second pair of eyes / approve

[barjin]

--legacy-peer-deps indeed doesn't seem to be necessary, tested locally.

[janbuchar]

Could you please change this to https://github.com/EndBug/add-and-commit so that it's consistent with the rest of the workflows that we manage?

[barjin]

cc @copilot you know what to do

[Copilot]

Done in ac7ff11 - switched to EndBug/add-and-commit@v9 with the same author config as bump-openapi-version.yaml.

[barjin]

this is curious, but we apparently have this in bump-openapi-version.yaml already, so at least we're consistent

[apify-service-account]

Preview for this PR was built for commit ac7ff11 and is ready at https://pr-2303.preview.docs.apify.com!