feat: use poetry for dependency mangement

[taddes]

Description

To align with other Python projects, the syncserver project should use poetry for Python dependency management.

There may be some initial variance from local tests and Docker in CI, given the CI env can yield different results.

This means the incorporation of the pyproject.toml files with matching poetry.lock files that pin dependencies. README.md files are updated with new conventions and Dockerflow files that used to call builds using pip are replaced with Poetry.

Testing

Running individual scripts with new poetry instructions. All README.md files are updated with Poetry and pyenv virtualenv instructions.

Issue(s)

Closes STOR-258.

[pjenvey]

With everything switched over to poetry except the Docker builds, can we remove the requirements.txt files entirely and simply have poetry generate them for us during those builds?

I like this first step approach but, even if it's temporary, I don't think we should have the dependencies duplicated in pyproject.toml and requirements.txt, especially when poetry can generate it for us e.g.

[pjenvey]

Suggested change