Separating remote download and publication stats

[himshikha]

Description

This change is aimed at providing granular metrics for remote download and overall remote incoming publication flow separately.

• Moved remote download failure stat to the RemoteClusterStateService download methods.
• Added new stat for remote publication failure during download.

          "remote_full_download" : {
            "success_count" : 1,
            "failed_count" : 0,
            "total_time_in_millis" : 4,
            "incoming_publication_failed_count" : 0,
            "checksum_validation_failed_count" : 0
          },
          "remote_diff_download" : {
            "success_count" : 2,
            "failed_count" : 0,
            "total_time_in_millis" : 12,
            "incoming_publication_failed_count" : 0,
            "checksum_validation_failed_count" : 0
          }

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

Check List

• [ ] Functionality includes testing.
• [ ] API changes companion pull request created, if applicable.
• [ ] Public documentation issue/PR created, if applicable.

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[bot]]

:x: Gradle check result for 72d5889c30cf117f1536be71c23559d133c5b26a: FAILURE

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?

[soosinha]

Can you update the description with why this change is needed ?

[himshikha]

I am assuming this won't break ser/de(BWC) with version upgrades

Since we are only adding new field, it shouldn't break BWC

[github-actions[bot]]

:white_check_mark: Gradle check result for 61b8e44d44632424c061099a6263d96ebe966132: SUCCESS