Yakov/mlpiper restful refactoring

[yakov-g]

This repository is public. Do not put here any private DataRobot or customer's data: code, datasets, model artifacts, .etc.

Summary

@klichukb @eric-s-s @yura-ant
Here is the move of the component from mlpiper to drum.
I had to move a bit more extra files than I expected.
Most of these dependencies are there to make this things more generic and likely can be very simply removed.

This component is covered by functional tests, so this move works fine.

Would like to here your suggestions about this move? Do we want to merge it?

Rationale

[yura-ant]

That PR has just one unit test which I've added when implement ability to configure threads option in mlpiper. This is definitely not enough for such big changes

As reviewer I should be able to read unit tests to understood how proposed new functionality works and just after that review how it was implemented.

Some existing functional tests (which exactly are not clear from PR) in DRUM cover how mlpiper was integrated before and they not test all those classes which you plan to add. Those test are good as regression test to prove that expected integration with mlpiper continue works as before.

Basic rule is when you add a new function you should add unit test.
Once we follow it we have a lot benefits

Also this PR introduce a lot of duplicated classes one from mlpiper another one form drum which could lead to issues if user chose wrong import. Ideally if we remove completely dependency to mlpiper or remove those classes from mlpiper.