Review Usages of actionGet API Call

[adityaj1107]

Describe the bug
Review usages of actionGet API calls so that this API if being called in a single threaded pool should use timeouts or should be called asynchronously.

PRs in alerting (opensearch-project/alerting#130) and index management (opensearch-project/index-management#100) where we have replaced the usages of the actionGet API calls which are blocking in nature and block the execution of the program with the callback listeners for the API call response. Using this API with time outs is okay but the execution should be made asynchronous.

Sample Usage in Security:

security/src/main/java/org/opensearch/security/tools/SecurityAdmin.java

Line 565 in 13f888f

final AcknowledgedResponse response = tc.admin().indices().updateSettings((new UpdateSettingsRequest(index).settings(indexSettings))).actionGet();

security/src/main/java/org/opensearch/security/configuration/ConfigurationRepository.java

Line 216 in 13f888f

.actionGet()

security/src/main/java/org/opensearch/security/configuration/ConfigurationRepository.java

Line 232 in 13f888f

.waitForYellowStatus()).actionGet();

security/src/main/java/org/opensearch/security/auditlog/sink/InternalOpenSearchSink.java

Line 78 in 13f888f

irb.execute().actionGet();

We should review all such usages.

[davidlago]

We are doing some "spring cleaning in the fall", and to make sure we focus our energies on the right issues and we get a better picture of the state of the repo, we are closing all issues that we are carrying over from the ODFE era (ODFE is no longer supported/maintained, see post here).

If you believe this issue should still be considered for current versions of OpenSearch, apologies! Please let us know by re-opening it.

Thanks!