kvserver: allow retrying scatter processing with more errors

[kvoli]

Previously, scatter processing would only be retried when encountering a snapshot error. Other errors commonly occur, which we expect to be transient and retryable, such as the range descriptor changing or rejected lease transfers. The range descriptor change error being most common, due to the proclivity of clients to issue splits alongside scatter requests, which would update the range descriptor.

Retry failed scatter replicate processing if the returned error matches any of IsRetriableReplicationChangeErrors, similar to range splits. Note the maximum number of retries remains at 5 for scatter.

Resolves: #124522 Release note: None

[blathers-crl[bot]]

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?

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

[cockroach-teamcity]

This change is 

[dt]

Maybe while we're here we should rename maxAttempts and currentAttempt to maxSuccesses and successes to avoid confusing them with the retry attempt limit?

[kvoli]

bors r=nvanbenschoten

[craig[bot]]

Build succeeded:

• macos_amd64_build
• acceptance
• linux_amd64_build
• linux_arm64_build
• check_generated_code
• examples_orms
• macos_arm64_build
• docker_image_amd64
• unit_tests
• linux_amd64_fips_build
• local_roachtest_fips
• windows_build
• local_roachtest
• lint