Abstract GraphOptimiser from FEDOT

[gkirgizov]

Meta-issue for tracking progress about our Dream: making an ecosystem of application domains around one abstract and modular GraphOptimiser. After this issue we could begin transition of EPDE/BAMT/Gefest and possibly others onto new architecture; while FEDOT will be using this GraphOptimiser in the domain of AutoML.

These are the steps that I see as necessary for this:

• [x] #608
• [ ] #705
• [x] #706
• [ ] Likely needed a better definition of Composer / ComposerBuilder and separation of their responsibilities
• [x] Define responsibilities of the base GraphOptimiser, especially wrt EvoGraphOptimiser. Maybe it will be just an abstract interface, maybe it will handle some infrastructural functions (logging/timing/history/stop conditions). Mostly closed by #787
• [x] #850
• [ ] #788
• [ ] #866

You can link to this issue any thoughts/features/requirements you have in mind about GraphOptimiser.

[nicl-nno]

This PR also can be useful, since it describes the features required for integration with GEFEST and other non-graph solutions.

[gkirgizov]

Текущая архитектура just for reference

[gkirgizov]

closed with #989