Lock down poetry version in our github actions / CI

[vevetron]

User story / feature request

Currently our build pipeline pulls the latest poetry version and installs it. As the poetry versions update commands and features start to deprecate. When it went from 1.8.5 to 2.0.0, all of our poetry profiles stopped working correctly due to new lines needed. Also currently our build is failing since the export command got removed to a secondary package.

Acceptance Criteria

So that we waste less time chasing fixes each time the build breaks, I recommend we lock it down in all of our scripts like this (somehow adding some environmental variable):

  - run: curl -sSL https://install.python-poetry.org | POETRY_VERSION=2.0.1 python -

Notes

I'm open to discussion