Upgrade poetry.lock after updating Docker image to Python 3.10.13

[Shinnnyshinshin]

What does this PR do?

• Follow-up to Fix Python 3.10.13 container #215
• Re-attempting what Upgrade Docker image to Python 3.10.13 #205 tried tod.

Reference

• we are currently seeing failures in the containerize-agent stage of CI/CD : here

#11 47.69 Note: This error originates from the build backend, and is likely not a problem with poetry but with psutil (5.9.8) not supporting PEP 517 builds. You can verify this by running 'pip wheel --use-pep517 "psutil (==5.9.8)"'.

• Ran poetry update to update the poetry.lock file.
• The command was run in a python 3.10.13 environment, which matches Docker.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.77%. Comparing base (6ddc833) to head (e96bc4a).

❗ Current head e96bc4a differs from pull request most recent head 6839a46. Consider uploading reports for the commit 6839a46 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #208   +/-   ##
=======================================
  Coverage   81.77%   81.77%           
=======================================
  Files          26       26           
  Lines         944      944           
=======================================
  Hits          772      772           
  Misses        172      172           

Flag	Coverage Δ
3.10	81.77% <ø> (ø)
3.11	81.77% <ø> (ø)
3.8	81.65% <ø> (ø)
3.9	81.65% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Kilo59]

This update makes a lot of dependency changes.

• I would suggest waiting until [Maintenance] add dev docker tag to latest releases and pre-releases #207 merges, making this a pre-release, and doing some manual testing before merging this.

[Shinnnyshinshin]

ok great idea @Kilo59. I'll follow up here tomorrow.

[anthonyburdi]

Agree. @Kilo59 Would it make sense to revert the docker image bump PR as well in the meantime? I'm thinking yes. #205 Then incorporate that change with this in a pre-release as you suggested.

[Kilo59]

Suggested change

	RUN apt-get install --no-install-recommends libpq-dev python-dev build-essential libsnappy-dev
	RUN pip --no-cache-dir install poetry==1.6.1
	RUN pip --no-cache-dir install poetry==1.8.2

Not sure why I didn't notice this earlier, but this is an old version of poetry.

Try reverting the extra apt-get commands and seeing if this by itself fixes it.

[Kilo59]

The command was run in a python 3.10.13 environment, which matches Docker.

Just to note, whether or not the lock command was run in a python 3.10.13 environment is largely irrelevant.

• update deps #214

[Shinnnyshinshin]

Thank you @Kilo59. This really helps clear up my understanding :)