[Segment Replication] Add logic back to update tracking replication checkpoint on source

[dreamer-89]

Description

With #8020, the behavior around how primary tracks replica checkpoint was changed. The change was to rely on replica shard initiating a separate transport call to primary for checkpoint update when segment replication round finishes. This additional network call breaks backward compatibility with released versions where source does not have respective transport handler to update target replication checkpoint and fails with below error

Failed to update visible checkpoint for replica [test-index-segrep][2], ReplicationCheckpoint{shardId=[test-index-segrep][2], primaryTerm=1, segmentsGen=4, version=9, size=230, codec=Lucene95}: RemoteTransportException[[v2.8.1-2][127.0.0.1:36499][internal:index/shard/replication/update_visible_checkpoint]]; nested: ActionNotFoundTransportException[No handler for action [internal:index/shard/replication/update_visible_checkpoint]];

This PR now allows the primary to update the visible ReplicationCheckpoint of replica shards with node-node communication. In current state:

1. Node-Node communication. Source updates replication checkpoint as part of get_segment_files handling
2. Remote store. Source expects replica shard to make update_visible_checkpoint transport call.

Related Issues

Resolves #8322
Related: #8202

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/19544/
• CommitID: bd015d1
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/19724/
• CommitID: b84762d
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/19739/
• CommitID: 940fe8f
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/19745/
• CommitID: f0f7bb3
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/19763/
• CommitID: 23a2f0f
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/19769/
• CommitID: 7c50cb1

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-8560-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 3d7d33bdbc02ec8e363c5394a9d89451f76e979a
# Push it to GitHub
git push --set-upstream origin backport/backport-8560-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-8560-to-2.x.