Enable Local CI (aka Daggerize)

[blaisep]

Currently the CI takes 29 minutes and it has pinned dependencies in other repos.

I intend to implement local CI so that:

• We can easily rotate external dependencies
• We can iterate faster (by caching intermediate artifacts)
• Developers can follow the dependency tree more easily. (gitmodules don't get cloned locally)

Investigate dagger as the local build agent.

[blaisep]

Why local CI?

Overall, the development and documentation of this effort can be simplified by supporting CI locally in the repo, rather than depending on github and submodules. ( see: https://github.com/blaisep/pytest-bdd-ng/commit/1d7aad7787ecf56a0d2d1ea5ea4812d8383ab72f )

For example, when @The-BDD-Coach asks

"where is the source for the Step object?

It turns out that it's in a different repo altogether, the messages repo

So I think it would be useful to run a bit of code using dagger to run the CI and access the git sub-modules directly

TODO: look up dagger python SDK code

• Is the approach to add the messages repo as a directory to the working container?
• Or is it better to do a multi-stage build ?
• Or is the answer to do both?

I want to make it easy to matrix so that developers can try newer/older versions of the external dependencies.