Implementation of RemoteWritableEntity for objects to uploaded to remote store

[soosinha]

Description

This change implements the interface created in the PR #13785. The implementation is done for the objects which need to be uploaded to remote store.

Related Issues

NA

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• API changes companion pull request created.
• Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)
• Public documentation issue/PR created

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 result for 6842837: 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?

[github-actions]

❌ Gradle check result for ee52329: 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?

[Bukhtawar]

Looks like the PR needs to be refreshed based on the #13785

[github-actions]

✅ Gradle check result for a2aafaa: SUCCESS

[codecov]

Codecov Report

Attention: Patch coverage is 92.98246% with 12 lines in your changes missing coverage. Please review.

Project coverage is 71.73%. Comparing base (b15cb0c) to head (a2aafaa).
Report is 371 commits behind head on main.

Files	Patch %	Lines
...ay/remote/model/RemoteClusterMetadataManifest.java	75.60%	6 Missing and 4 partials ⚠️
...rch/gateway/remote/model/RemoteCustomMetadata.java	96.42%	1 Missing ⚠️
...rch/gateway/remote/model/RemoteGlobalMetadata.java	88.88%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #13834      +/-   ##
============================================
+ Coverage     71.42%   71.73%   +0.31%     
- Complexity    59978    61692    +1714     
============================================
  Files          4985     5089     +104     
  Lines        282275   289404    +7129     
  Branches      40946    41858     +912     
============================================
+ Hits         201603   207603    +6000     
- Misses        63999    64661     +662     
- Partials      16673    17140     +467     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[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:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-13834-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 49282c111c593bb2b1ee76b50102c06fa1f2c627
# Push it to GitHub
git push --set-upstream origin backport/backport-13834-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x

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