feat: Caraml sdk commons

[maniteja6799]

• CaraML client created that wraps on top of existing models, turing clients
• MLP module created, which will be used by all the other clients (caraml, models, turing)
• modules moved to a new package, making imports look like from caraml.models.transformer import Transformer
• Sample notebook added to showcase caraml client usage caraml-sdk/examples/sklearn

[Existing Issues]

• Routers client is commented in caraml client as of now because of the following issue:

All over turing wrapper code, the imports are not used well. There are pieces like this response = caraml.routers.active_session.list_ensembling_jobs( ...) all through the code. I've fixed all the instances for in-code imports, But there are these usages for active sessions using global static objects inside a class definition. The package is inconsistent with different formats used at different parts of the turing code. All the classes are using a global active_session object added in the turing package init.py file

PS: Please ignore the number of commits in this PR. I've created a branch from my forked repo, and the merge in the base repo is a squashed commit.

[maniteja6799]

Note: Pytests in models, routers are failing.

For Models package. there are issues with pytest only since it looks for current module first packages while figuring imports and there is a conflict in names for the current caraml-sdk packages (caraml.routers/models/common.*) vs caraml upi packages loaded into site-packages under sys path (caraml.upi.*).

Routers tests are failing due to various reasons, After the refactor to use the caraml package as the base package for import statements inside wrapper code, there are discrepancies and inconsistencies in some files that are making issues for tests to run.

[maniteja6799]

For Models package. there are issues with pytest only since it looks for current module first packages while figuring imports and there is a conflict in names for the current caraml-sdk packages (caraml.routers/models/common.) vs caraml upi packages loaded into site-packages under sys path (caraml.upi.).

Regarding this, trying out some monkey patching to get caraml.upi working like mentioned here: pytest-dev/pytest#5147 (comment)