Upgrade to python 3.10

[Jovian-Dsouza]

Summary

Description of the change(s) you made

• Updates docker images, including production's, to use python:3.10-slim-bookworm base, thereby upgrading python to 3.10
• Other relevant changes making the new minimum supported version of studio to be 3.10

Manual verification steps performed

• Run make dcbuild then make dcup and everything ran fine through docker
• Run docker build -f k8s/images/app/Dockerfile . and built the production image successfully

Does this introduce any tech-debt items?

No this removes tech-debt

---

Reviewer guidance

How can a reviewer test these changes?

As mentioned above

Are there any risky areas that deserve extra testing?

• Merging risk

References

Solves #4211

Comments

We can also consider updraging to Node 18.x since Node 16.x is deprecated

---

Contributor's Checklist

PR process:

• If this is an important user-facing change, PR or related issue the CHANGELOG label been added to this PR. Note: items with this label will be added to the CHANGELOG at a later time
• If this includes an internal dependency change, a link to the diff is provided
• The docs label has been added if this introduces a change that needs to be updated in the user docs?
• If any Python requirements have changed, the updated requirements.txt files also included in this PR
• Opportunities for using Google Analytics here are noted
• Migrations are safe for a large db

Studio-specifc:

• All user-facing strings are translated properly
• The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)
• All UI components are LTR and RTL compliant
• Views are organized into pages, components, and layouts directories as described in the docs
• Users' storage used is recalculated properly on any changes to main tree files
• If there new ways this uses user data that needs to be factored into our Privacy Policy, it has been noted.

Testing:

• Code is clean and well-commented
• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical user journeys are covered by Gherkin stories
• Any new interactions have been added to the QA Sheet
• Critical and brittle code paths are covered by unit tests

---

Reviewer's Checklist

This section is for reviewers to fill out.

• Automated test coverage is satisfactory
• PR is fully functional
• PR has been tested for accessibility regressions
• External dependency files were updated if necessary (yarn and pip)
• Documentation is updated
• Contributor is in AUTHORS.md

[rtibbles]

Thanks for this - a quick skim over the code gave me no cause for concern - just one repeated typo and one question.

Will need to do some manual testing before approval.

[rtibbles]

Local manual testing checks out. This is good to merge. Thank you @Jovian-Dsouza !