Refactors the managed index runner to work with extensions

[downsrob]

Issue #, if available:
NA

Description of changes:

• Adds NewClusterEventListeners so that extensions may react to cluster events with the NewCluster type
• Supports transition condition evaluation for non-default index types by using the IndexMetadataProvider to get the index creation date. Adds caching of the index creation date for all index types to the ManagedIndexRunner
• Adds a setting to deleteIndexMetadataAfterFinish to actions. When set to true, the managed index config and metadata for the index that the policy/action is attached to will be deleted following action completion. For in-cluster indices this should be handled automatically, so this setting is just to support this behavior for custom actions on non-default index types.
• Adds IndexMetadataProvider implementation from Makes rest APIs use new metadata service #245 Changes to the IndexMetadataProvider may need to be made to either PR based on the other's comments. This is awkward, but it is a blocker otherwise.
• Code cleanup

CheckList:

• Commits are signed per the DCO using --signoff

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.

[codecov-commenter]

Codecov Report

Merging #262 (ade5565) into development-extension (40544b8) will decrease coverage by 0.12%.
The diff coverage is 41.08%.

@@                     Coverage Diff                     @@
##             development-extension     #262      +/-   ##
===========================================================
- Coverage                    73.20%   73.07%   -0.13%     
- Complexity                    1836     1856      +20     
===========================================================
  Files                          252      252              
  Lines                        10969    11047      +78     
  Branches                      1697     1726      +29     
===========================================================
+ Hits                          8030     8073      +43     
- Misses                        1950     1979      +29     
- Partials                       989      995       +6     

Impacted Files	Coverage Δ
...ment/indexstatemanagement/IndexMetadataProvider.kt	65.62% <ø> (ø)
...ent/indexstatemanagement/util/ManagedIndexUtils.kt	63.39% <25.00%> (-6.10%)	⬇️
...agement/indexstatemanagement/ManagedIndexRunner.kt	36.34% <30.50%> (+3.00%)	⬆️
...anagement/step/transition/AttemptTransitionStep.kt	76.00% <50.00%> (-14.13%)	⬇️
...ndexmanagement/indexstatemanagement/model/State.kt	88.88% <80.00%> (-1.59%)	⬇️
...temanagement/opensearchapi/OpenSearchExtensions.kt	68.96% <85.71%> (+0.36%)	⬆️
...pensearch/indexmanagement/IndexManagementPlugin.kt	88.57% <100.00%> (+0.04%)	⬆️
...t/indexstatemanagement/action/TransitionsAction.kt	100.00% <100.00%> (ø)
...nt/indexstatemanagement/model/destination/Chime.kt	40.90% <0.00%> (-13.64%)	⬇️
...ndexstatemanagement/IndexStateManagementHistory.kt	77.30% <0.00%> (-1.42%)	⬇️
... and 18 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 40544b8...ade5565. Read the comment docs.

[dbbaughe]

Is this new code or just existing code refactored to this place?

[downsrob]

It's a generalization of the isSuccessfulDelete function:
https://github.com/opensearch-project/index-management/blob/main/src/main/kotlin/org/opensearch/indexmanagement/indexstatemanagement/util/ManagedIndexUtils.kt#L430-L433
The purpose is that if an extension creates an action to delete their off cluster index, then they can set deleteIndexMetadataAfterFinish to true in the custom action, and then after it isFinishedSuccessfully, the metadata will be deleted for the action.
Thinking about this a bit more now, I can add an additional validation here to make it so these extension actions which set deleteIndexMetadataAfterFinish = true can't transition or have actions after the delete

[downsrob]

I do see a logical error in the code though, if (policyRetryInfo == null || policyRetryInfo.failed) return false would mean that the action would never be noted as isFinishedSuccessfully if the policyRetryInfo was null. It is initialized with the metadata so it shouldn't be a problem but I will change that as well

[bowenlan-amzn]

Good good