feat: add poetry 1.8.4 -> 2.1.2

[sgaist]

Summary

This PR adds all poetry versions from 1.8.4 up to current (at the time of PR creation) 2.1.2

Fixes #472
Supersedes #470

Use Cases

Allow buildpack user to have more recent versions of poetry at their disposal.

Checklist

• I have viewed, signed, and submitted the Contributor License Agreement.
• I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
• I have added an integration test, if necessary.
• I have reviewed the styleguide for guidance on my code quality.
• I'm happy with the commit history on this PR (I have rebased/squashed as needed).

[katrilh]

@sgaist or potentially @arjun024 any chance we can get some attention to this PR and get it approved/merged? 🤞🏼

[sgaist]

@katrilh As the PR author, what can I do to help move it forward ?

[katrilh]

@sgaist Do you know of a way to bump this for the paketo-buildpacks/python-maintainer-group?
Thank you so much for opening the PR ❤️ This opening this PR -- poetry has released versions upto 2.1.2 any chance could be added in too?

[a1flecke]

@katrilh @sgaist I am also very interested in this PR. I started a discussion asking how to get attention to this PR. So far, no info.

[sgaist]

@katrilh new versions added as requested :-)

@a1flecke another possible thing to do is join one of the community calls and check with the folks there if there's something that could be done to help push things forward.

[jericop]

Apologies for not seeing this sooner. I'm taking a look.

[sgaist]

@jericop I updated the version of actions/upload-artifact to v4 which should also fix other automated pipelines that are failing such as the one that should do the auto-update.

[jericop]

Thanks for updating the upload-artifact from v3 to v4. I reviewed the migration guide and was not sure if it would cause any failures due to overwrites no longer allowed by default, so I went ahead and tested it and it looks like it should be good to go. You can ignore my closed PRs on your fork. Those were opened by mistake.

One more thing that you could add to this PR to avoid the push-buildpack workflow from failing is to disable GCR image push by commenting it out here.
https://github.com/idiap/paketo-buildpacks-poetry/blob/21738b75cf844a9a0b3e6c5a09d142c9d0619112/.github/workflows/push-buildpackage.yml#L42-L50

After that it should be good to go.

[sgaist]

@jericop Done as requested !

Should the GCR disabling be applied to other buildpacks as well ?

I was thinking about going through the python related buildpacks to fix the upload-artifact actions.

[jericop]

Should the GCR disabling be applied to other buildpacks as well ?

I was thinking about going through the python related buildpacks to fix the upload-artifact actions.

That would be great. Thank you!

[mzuber]

@jericop Bringing this change upstream seems to require some changes to the integration tests in the paketo-buildpacks/python buildpack. I tried to address this in paketo-buildpacks/python#1028, maybe you can have a look into this as well.