Base extractor

[einarmo]

First take on a new base extractor class. Some more work goes into this in the next step, adding startup reporting and integrating things a bit more tightly, but this is a nice first draft that contains some of the core logic.

The base extractor has a few roles, currently:

• It contains the config object, in the future it will also handle changes to config revision and restart.
• It acts as an error reporter, for raw errors.
• It manages "monitored tasks", which are essentially just C# Tasks. The idea is that if something fails in a background process, this needs to be properly reported to the extractor so that it can take appropriate action. Background tasks have a name, can be cancelled independently, and can be expected to end or not, so if a task ends without an error, the extractor can take appropriate action.
• It also contains shutdown logic, which is highly customizable, since extractor implementations may want to shut components down in a specific order. In general, different parts of the process are supposed to be independently cancelled, so that graceful shutdown is possible.

As with the last iteration of the base extractor, it is intended to be used as a base class for user extractors.

[codecov]

Codecov Report

Attention: Patch coverage is 78.94737% with 44 lines in your changes missing coverage. Please review.

Project coverage is 78.24%. Comparing base (8b44bc4) to head (dc23272).
Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
ExtractorUtils/Unstable/BaseExtractor.cs	84.14%	9 Missing and 17 partials ⚠️
...ctorUtils/Unstable/Tasks/ExtractorTaskScheduler.cs	60.00%	11 Missing and 7 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #522      +/-   ##
==========================================
+ Coverage   78.10%   78.24%   +0.13%     
==========================================
  Files         123      124       +1     
  Lines       11541    11748     +207     
  Branches     1748     1781      +33     
==========================================
+ Hits         9014     9192     +178     
- Misses       1817     1822       +5     
- Partials      710      734      +24     

Files with missing lines	Coverage Δ
ExtractorUtils/Unstable/Tasks/CheckInWorker.cs	76.29% <ø> (ø)
ExtractorUtils/Unstable/Tasks/Errors.cs	97.43% <ø> (ø)
...ctorUtils/Unstable/Tasks/ExtractorTaskScheduler.cs	65.04% <60.00%> (-1.12%)	⬇️
ExtractorUtils/Unstable/BaseExtractor.cs	84.14% <84.14%> (ø)

... and 4 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ozangoktan]

For the IIntegrationSink, I am starting to think sink may not be the best choice to describe it as. Isn't what it is doing something like an IOrchestratorIntegration rather than a sink adapting to an integration, which could mean other things than integrations api orchestrating the extractor.

[einarmo]

Let's do renaming the sink in a different PR, if we are doing it. It's a bit intrusive for this one.

[finnag]

🦄