build: improve security around package updating

[georgeRobertson]

TLDR of changes

• Updated poetry to v2.4 to allow usage of https://python-poetry.org/docs/configuration#solvermin-release-age which prevents newly released packages from being updated until they're at least 10 days old.
• Locked the boto3 and botocore package

What kind of changes does this PR introduce?

Tick all that apply

• fix: A bug fix. Correlates with PATCH in SemVer
• feat: A new feature. Correlates with MINOR in SemVer
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• refactor: A code change that neither fixes a bug nor adds a feature
• perf: A code change that improves performance
• test: Adding missing or correcting existing tests
• build: Changes that affect the build system or external dependencies (example scopes: pip, docker, npm)
• ci: Changes to CI configuration files and scripts (example scopes: GitLabCI)

Please check if the PR fulfills these requirements

• I have read and followed the Contributing guidance
• Docs have been added / updated
• Tests and Linting in the CI are passing
• Changes have been reviewed and approved by a Project Maintainer

[sonarqubecloud]

Quality Gate failed

Failed conditions
E Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE