Migrate AnomalyResultAction/TransportAction to SDK using the SDKClient

[joshpalis]

Is your feature request related to a problem?

Part of #383

After the AnomalyDetectorJobRunner is executed by Job Scheduler, AD creates a AnomalyResultRequest and invokes the AnomalyResultAction here.

To complete the start detector workflow, it is necessary to :

• Add the AnomalyResultAction Action Handler to the getActions extension point
• Add the RCFResultAction Action handler to the getActions extension point
• Add the EntityResultAction Action handler to the getActions extension point
• Add the ADResultBulkAction Action handler to the getActions extension point
• Integrate AnomalyResultTransportAction with the SDKClient/ClusterService
• Integrate EntityResultAction with the SDKClient/ClusterService (multi-entity detector)
• Integrate RCFResultAction/TransportAction with the SDKClient/ClusterService (single-entity detector)
• Integrate ProfileTransportAction with SDKClient/ClusterService (used to update realtime high cardinality detector)
• Integrate the following components in createComponents extension point needed for the AnomalyResultTransportAction, EntityResultTransportAction :
  • NodeStateManager
  • FeatureManager
  • ModelManager
  • ADCircutBreakerService
  • ADStats
  • ADTaskManager
  • IndexNameExpressionResolver
  • EntityColdStartWorker
  • MultiEntityResultHandler
  • ResultWriteWorker
  • CheckPointReadWorker
  • ColdEntityWorker
• Fix any affected test classes

Blockers for multi-entity detector results

• Implement IndexingPressure as a created component ([FEATURE] Add support in the SDK to retrieve IndexingPressure information from OpenSearch #655)
• Integrate the ADResultBulkAction with the SDK (invoked by the MultiEntityResultHandler to index anomaly results for multi-entity (HC/HCAD) detectors). (Migrate ADResultBulkAction/TransportAction and Multi-Entity real time analysis #684) Dependent on [FEATURE] Add support in the SDK to retrieve IndexingPressure information from OpenSearch #655