Separate Remote State and Publication enabled and configured methods

[shiv0408]

Description

Currently we have references to isRemoteStateEnabled and isRemotePublicationEnabled methods at multiple places. We want to create different methods isRemoteStateConfigured and isRemotePublicationConfigured, which will return true if node attributes are present on the node.

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 60fbfea: 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 69b1724: 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 e5d3abc: 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 87a8e84: 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 831359c: 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 122a549: 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 cfcb605: 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.

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 7 lines in your changes missing coverage. Please review.

Project coverage is 71.94%. Comparing base (8ddb3ee) to head (9f59e2b).
Report is 19 commits behind head on main.

Files with missing lines	Patch %	Lines
...g/opensearch/cluster/coordination/Coordinator.java	25.00%	2 Missing and 1 partial ⚠️
...search/cluster/coordination/CoordinationState.java	0.00%	0 Missing and 1 partial ⚠️
...arch/gateway/remote/RemoteClusterStateService.java	50.00%	0 Missing and 1 partial ⚠️
...ensearch/index/remote/RemoteIndexPathUploader.java	0.00%	0 Missing and 1 partial ⚠️
...rch/node/remotestore/RemoteStoreNodeAttribute.java	0.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #16080      +/-   ##
============================================
+ Coverage     71.86%   71.94%   +0.08%     
- Complexity    64447    64500      +53     
============================================
  Files          5288     5288              
  Lines        301438   301436       -2     
  Branches      43552    43551       -1     
============================================
+ Hits         216628   216878     +250     
+ Misses        67034    66797     -237     
+ Partials      17776    17761      -15     

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

[github-actions]

❌ Gradle check result for 70947b5: 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 9f59e2b: SUCCESS