Refactor Threat Intel Feeds Job Scheduler

Refactor threat intel feeds job scheduler to decouple it with creating and updating IOCs.

Part 1.
Refactor the transport layer into a service class that DetectorThreatIntel directly calls.

Part 2.

• Renamed TIFJobUpdateService to ThreatIntelFeedIndexService
• Renamed TIFJobParameter to TIFJobSchedulerMetadata
• Refactored ThreatIntelFeedDataService and ThreatIntelFeedIndexService so that threat intel indices are created and deleted in the ThreatIntelFeedIndexService class but the data is parsed and saved into the index in the ThreatIntelFeedDataService class to provide better modularization.

More specifics to the refactoring
Methods moved from ThreatIntelFeedDataService to ThreatIntelFeedIndexService

• getIndexMapping
• createIndexIfNotExists
• deleteThreatIntelDataIndex
• createIndexIfNotExists

Methods moved from ThreatIntelFeedIndexService to ThreatIntelFeedDataService

• updateJobSchedulerMetadataAsSucceeded
• waitUntilAllShardsStarted

Refactored

• createThreatIntelFeedData to createThreatIntelFeed in ThreatIntelFeedIndexService, refactored so groupedActionListener is done in data service where it uses the csvParser to parse and save feeds into the index. This method is the hook for ThreatIntelHighLevelHandler and TIFJobRunner to set up and create a TIF index as well as populating it with data in ThreatIntelFeedDataService

Locate DetectorThreatIntel, ThreatIntelFeedDataService, ThreatIntelFeedIndexService, TIFJobSchedulerMetadata, ThreatIntelHighLevelHandler, and TIFJobRunner. Read the current scheduler and transport interactions first, then trace the listed methods and their callers. Done means the renamed services and metadata are wired correctly, with index lifecycle separated from feed parsing and persistence.