Add CICD test for orchestrator using Dagger

[bnchrch]

What

We need to run orchestrator unit tests in CICD

closes #24209

How

This adds that using a dagger pipeline

Notes for reviewer

Not using an alpine image

Unfortunately dagster using the grpcio library which currently doesnt have "wheel" binaries for alpine. So to avoid 10 minute plus recompile times I changed to use a debian base package

Interesting reading:
https://medium.com/swlh/alpine-slim-stretch-buster-jessie-bullseye-bookworm-what-are-the-differences-in-docker-62171ed4531d
grpc/grpc#22815
grpc/grpc#24722

Poetry sibling modules

I updated with_poetry to let you copy a parent working directory of the poetry module to allow for relative imports

[alafanechere]

Nice! My main concern is around file system access / mount, I suggest you use the get_repo_dir method of the context object if you need to mount directories to containers.

[alafanechere]

LGTM.
Please consider my suggestion about the with_poetry_module parameters.
I agree that we should favor the use of debian base images, but please keep also what've been on top of alpine so far. My work on this PR has a lot of moving pieces that I think I succeeded in keeping stable and I'd prefer to not change the base images I used so far. I'll create an issue to do it later.

[alafanechere]

Do we really need to enable the editable mode while running in a CI context?

[bnchrch]

Without -e we were getting this failure.
https://github.com/airbytehq/airbyte/actions/runs/4632791811/jobs/8197275855?pr=24816

Seems like some weird caching behaviour with the hostedtools cache.

As the version 0.2.1 is most recent but its certainly trying to reference code from <0.2.0

When looking around the code base though it seems like in the majority of actions where we install tools/ci_* we are using the -e flag.

I imagine for this reason.