Build a yaml version of the pipeline descriptor

[fpacifici]

The python version of the pipeline descriptor is great for application that are defined inside a python code base.
If a pipeline is built in rust or across multiple code bases this is not so great.

Try to build a pipeline definition in yaml that would generate the same graph and see how that looks like.

[fpacifici]

1. Read this https://www.notion.so/sentry/DACI-How-do-we-wire-operators-with-each-other-in-the-pipeline-1a58b10e4b5d80ff8f73f55b7feb4405. We picked option 1
2. Adopt this option https://www.notion.so/sentry/DACI-How-do-we-wire-operators-with-each-other-in-the-pipeline-1a58b10e4b5d80ff8f73f55b7feb4405?pvs=4#1b68b10e4b5d80a180dceeec52754d69
3. This is the place where we load the pipeline https://github.com/getsentry/streams/blob/main/sentry_streams/sentry_streams/runner.py#L137-L141. This is going to be the entry point where we would load the yaml version rather than the python one.

Things to watch out for:

• The yaml version can only load classes and functions dynamically. How does this fit with typing in the pipeline class assuming steps will be generic and have types.
• tentative: first step is building something equivalent to python. If you want to try to wire up segments of pipelines defined in separate images it would be appreciated.