Use remote publication flag to decide which custom objects to upload

[soosinha]

Description

This PR addresses the following:

• Cluster state customs should only be uploaded when remote publication is enabled.
• All metadata customs when remote publication is enabled while customs with context as GATEWAY should be uploaded otherwise
• simplify the logic of computing the updated customs
• Fix bug where metadata customs map was being used to remove cluster state customs to be deleted.
• Close input stream while reading blob

Related Issues

NA

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]

❌ Gradle check result for 597057a: 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 0ab67e6: 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 8f3c702: 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 3a342c6: 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]

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

Flaky test: #14296

[github-actions]

❌ Gradle check result for 4a12c2e: 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 18eceb7: SUCCESS

[codecov]

Codecov Report

Attention: Patch coverage is 88.57143% with 8 lines in your changes missing coverage. Please review.

Project coverage is 71.77%. Comparing base (b15cb0c) to head (ac465ba).
Report is 433 commits behind head on main.

Files	Patch %	Lines
...arch/gateway/remote/RemoteClusterStateService.java	76.47%	1 Missing and 7 partials ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #14338      +/-   ##
============================================
+ Coverage     71.42%   71.77%   +0.35%     
- Complexity    59978    62088    +2110     
============================================
  Files          4985     5118     +133     
  Lines        282275   291833    +9558     
  Branches      40946    42180    +1234     
============================================
+ Hits         201603   209460    +7857     
- Misses        63999    65057    +1058     
- Partials      16673    17316     +643     

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

[github-actions]

✅ Gradle check result for e7bc511: SUCCESS

[github-actions]

❕ Gradle check result for ac465ba: UNSTABLE

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.