Scheduler

[yalosev]

Overview

• Reworking the mechanism of detecting which modules are enabled/disabled and by which components;
• RunModuleWithNewStaticValues method was rewritten to RunModuleWithNewOpenAPISchema (and it's logic, from updating a module's static values to updating its schema storage;
• A module status changed event is sent if the module's enabled status wasn't changed, but the reason why module is enabled/disabled has changed.

What this PR does / why we need it

This pr introduces a new sub-component of Module Manager - Module Scheduler, which aim is to decide which Module Manager's modules should be enabled or disabled by means of calculating a graph of the modules (DAG), traversing the graph and applying various module Filters (called Extenders). Currently, there are four basic extenders to filter modules' status:

• static (based on static values files)
• dynamic (based on catching global hooks' patches)
• kube-config (based on the values provided in the comfigMap)
• script-enabled (based on the results of running modules' enabled scripts)
  The order extenders applied is up to the user, yet a default list of applied extenders is provided. It's up to the user to add any new extenders, following provided extender interface.

Also, there are numerous changes to other components of the operator in the pr to suit the new graph-based model.

Special notes for your reviewer