Add tests for poetry

[gmargaritis]

Resolves #8

[parisk]

I would suggest taking a simpler approach on the CI level here, although the tests are 💯. A few suggestions:

• Run tests on the whole matrix on every push, so that we know our commits work as expected.
• If tests succeed, push image to GHCR tagged with ${github.sha}-{EXPECTED_RELEASE_TAG} (e.g. 95db419-1.7.1-python-3.12-bookworm)
• On release, tag the existing Git SHA tagged image on GHCR with the release version (e.g. 1.7.1-python-3.12-bookworm)

[gmargaritis]

@parisk Let me know how to proceed from here. What changes do we want to make in the release workflow?

[parisk]

I have added a few comments to tidy this up. We should also update the release workflow to just tag the images that already exist in the registry.

[gmargaritis]

@parisk How does pulling of existing images based on the git sha work? Wouldn't the git sha be different for the commit that triggered the ci workflow, from the one that triggered the release workflow?

[parisk]

Nope, it's pretty much the same commit. All releases should happen on the main branch, for which the CI pipeline should always run: https://github.com/withlogicco/docker-poetry/pull/48/files#diff-b803fcb7f17ed9235f1e5cb1fcd2f5d3b2838429d4368ae4c57ce4436577f03fR4-R6.

[parisk]

Great work. A few more tweaks and we should be good to go!

[parisk]

LGTM 🦌