[dagster-pipes-rust] - Inital integration with the pipes test suite

[marijncv]

Summary & Motivation

This sets up the initial integration with the dagster-pipes-tests suite. Most of the tests are skipped right now, they can be enabled incrementally.

The tests are run from a binary that is only included in the build if the optional pipes-tests feature is enabled. This keeps the main library slim.

Contributes to #58

How I Tested These Changes

cd libraries/pipes/implementations/rust
uv run pytest

Changelog

Ensure that an entry has been created in CHANGELOG.md outlining additions, deletions, and/or modifications.

See: keepachangelog.com

[danielgafni]

I wonder if it would be more appropriate to disable all tests in pipes.toml instead (so that they are skipped) rather than having no-op tests.

1. It would more explicitly communicate that there are no tests written yet.
2. It would make it easier to incrementally enable them one by one.

On a side note, the tests CLI args are not stabilized yet, we will be standardizing them next week with @GingerYouth for Java

[marijncv]

I wonder if it would be more appropriate to disable all tests in pipes.toml

That's a good point! I set all (skippable) tests to be skipped now.

the tests CLI args are not stabilized yet

That is good to know. I'll probably keep this PR in draft for a bit longer to work out how to deal with the clap dependency and to see if this setup works with one of the --full tests

[danielgafni]

I think it's ok to start working on the tests. We will probably remove the --full flag (as it's almost always set to true) and do a bit changes here and there. It's not going to be a lot of changes. Just fyi.

[danielgafni]

LGTM! just a small naming comment