Tsmith/poetry

[Bento007]

Reason for Change

• #TICKET_NUMBER
• If the reason for this PR's code changes are not clear in the issue, state value/impact

Changes

• use poetry to manage python dependencies
• move all python requirements files the python_dependencies directory.
• update dockerfiles to include the relevant python dependencies
• add make recipe to generate requirements and requirement-dev files for each container
• rename backend to api-server where backend is referring to api-server.
• separate development dependencies from software dependecies.

Testing steps

• Either list QA steps or reasoning you feel QA is unnecessary
• Describe how you made sure to know that your changes worked. Should allow someone else to go verify your code without in depth knowledge.
• "Unit tested only", "tested in rdev by a, b, c, verifying feature worked by... ", "manually ran pipeline locally with these results: ..."

Checklist 🛎️

• Add product, design, and eng as reviewers for rdev review
• For UI changes, add screenshots/videos, so the reviewers know what you expect them to see
• For UI changes, add e2e tests to prevent regressions

Notes for Reviewer

[Bento007]

breaking up into several smaller PRs