chore: separate pipeline client into sync and async clients

[faymarie]

Related Issues

• split pipeline client into sync and async clients to be better in line with the rest of of repo structure and documentation
• adds new modules to README generation

Directory changes:

• no more pipeline_client directory
• created separate client for AsyncPipelineClient in async client directory
• pipeline_client moved to sync_client directory, inherits for AsyncPipelineClient
• pipeline modules moved to the top-level moduls
• pipeline_service moved to service directory

Proposed Changes?

How did you test it?

Notes for the reviewer

Screenshots (optional)

Checklist

• I have updated the referenced issue with new insights and changes
• If this is a code change, I have added unit tests
• I've used the conventional commit specification for my PR title
• I updated the docstrings
• If this is a code change, I added meaningful logs and prepared Datadog visualizations and alerts

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
deepset_cloud_sdk
__init__.py
models.py
deepset_cloud_sdk/_service
pipeline_service.py
deepset_cloud_sdk/workflows
__init__.py
deepset_cloud_sdk/workflows/async_client
async_pipeline_client.py
deepset_cloud_sdk/workflows/sync_client
pipeline_client.py
Project Total

This report was generated by python-coverage-comment-action

[ArzelaAscoIi]

some nits around the inheritance/ naming.

already approving. I am also fine with doing it like this (reworking if required should be quickly doable if someone complains)

[ArzelaAscoIi]

THank you!

[faymarie]

Thanks for the hint of using composition. It's more straightforward indeed. Also renamed the method. @ArzelaAscoIi