kvserver: do not cancel while in HandleRaftResponse

[pav-kv]

If the context is canceled in the middle of HandleRaftResponse (after processQueue returns), a Replica can be left in a broken state, e.g. its destruction can be partially completed. This can brick a RangeID, e.g. cause a subsequent call to getOrCreateReplica to be stuck in an infinite loop.

This commit allows the HandleRaftResponse loop to terminate gracefully, by using a higher-level context which is not cancelable.

Fixes #140958, #145030

[blathers-crl]

It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR?

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[cockroach-teamcity]

This change is 

[tbg]

LGTM, thank you for looking into this.

[pav-kv]

TFTR!

bors r=tbg

[pav-kv]

bors cancel

[craig]

Canceled.

[pav-kv]

bors r=tbg

[craig]

🕐 Waiting for PR status (GitHub check) to be set, probably by CI. Bors will automatically try to run when all required PR statuses are set.

[craig]

Build succeeded:

• local_roachtest
• linux_amd64_fips_build
• local_roachtest_fips
• unit_tests
• linux_amd64_build
• docker_image_amd64
• lint
• check_generated_code
• acceptance
• examples_orms

[blathers-crl]

Encountered an error creating backports. Some common things that can go wrong:

1. The backport branch might have already existed.
2. There was a merge conflict.
3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.

---

💡 Consider backporting to the fork repo instead of the main repo. See instructions for more details.

error creating merge commit from 4273ead to blathers/backport-release-23.2-148965: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch release-23.2 failed. See errors above.

---

💡 Consider backporting to the fork repo instead of the main repo. See instructions for more details.

error creating merge commit from 4273ead to blathers/backport-release-24.1-148965: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch release-24.1 failed. See errors above.

---

💡 Consider backporting to the fork repo instead of the main repo. See instructions for more details.

error creating merge commit from 4273ead to blathers/backport-release-24.3-148965: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch release-24.3 failed. See errors above.

---

💡 Consider backporting to the fork repo instead of the main repo. See instructions for more details.

error creating merge commit from 4273ead to blathers/backport-release-25.1-148965: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch release-25.1 failed. See errors above.

---

💡 Consider backporting to the fork repo instead of the main repo. See instructions for more details.

error creating merge commit from 4273ead to blathers/backport-release-25.2-148965: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch release-25.2 failed. See errors above.

---

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[pav-kv]

Backporting this fix to 25.x versions. It could come up in earlier versions - if it does, we'll reconsider backporting further back.