Add sklearn compose models

[AHReccese]

Reference Issues/PRs

#263 #226

What does this implement/fix? Explain your changes.

Any other comments?

[AHReccese]

Hey folks, @sepandhaghighi @sadrasabouri
To avoid getting stuck, I prepared this PR. Some refactoring may still be needed and can be addressed in separate PRs (if you notice any). Please let me know your thoughts. I also tried to avoid going down rabbit holes in order to provide smooth, incremental updates.

After some minor PRs after this PR, we can have the 1.5 release.

[codecov]

Codecov Report

❌ Patch coverage is 84.21053% with 27 lines in your changes missing coverage. Please review.
✅ Project coverage is 74.83%. Comparing base (06716ac) to head (3e47bb4).
⚠️ Report is 150 commits behind head on dev.

Files with missing lines	Patch %	Lines
...transporters/general_data_structure_transporter.py	58.63%	7 Missing and 5 partials ⚠️
pymilo/transporters/compose_transporter.py	87.33%	4 Missing and 5 partials ⚠️
pymilo/chains/compose_chain.py	77.78%	6 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##              dev     #264       +/-   ##
===========================================
- Coverage   87.40%   74.83%   -12.56%     
===========================================
  Files          31       51       +20     
  Lines        1142     2455     +1313     
  Branches      201      451      +250     
===========================================
+ Hits          998     1837      +839     
- Misses         90      518      +428     
- Partials       54      100       +46     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

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

[sepandhaghighi]

@AHReccese

Thanks for your efforts. It's a giant pull request. I will review it within the next 5-6 days.

[sadrasabouri]

It looks good to me in general. I left some minor refactoring issues that can be addressed later in a separate PR, as you mentioned. I also raised a question about a default value.
Final review by @sepandhaghighi is necessary, though since this is a huge PR and I might have missed some logical code issues.

[AHReccese]

Thank you, Sadra @sadrasabouri, for your review. I will address them ASAP.
Sepand @sepandhaghighi, you can wait until I apply Sadra's feedback, and then I can ping you so that you can proceed with your review.

[AHReccese]

Thank you, Sadra @sadrasabouri, for your review. I will address them ASAP. Sepand @sepandhaghighi, you can wait until I apply Sadra's feedback, and then I can ping you so that you can proceed with your review.

Dear Sadra @sadrasabouri, I've applied your feedback, feel free to reach out to discuss more. We will do the review for this PR with only you (due to the current situation).

[sadrasabouri]

OK, I will review this soon. Please don't resolve the comments and let the reviewer do that. It helps with contextualizing.

[sadrasabouri]

Minor changes, which are again all refactors; Feel free to merge and fix them in future PR. It's up to you.