BB2-4684: Upgrade dockerfiles to slim-bookworm from trixie to address…

[JamesDemeryNava]

… Snyk issues

JIRA Ticket:
BB2-4684

What Does This PR Do?

Updates different Dockerfile's to use python:3.12-slim-bookworm rather than python:3.12-trixie. This removes imagemagick from the project, which is the package that has a vulnerability

What Should Reviewers Watch For?

If you're reviewing this PR, please check for these things in particular:

• Any concerns about switching to slim-bookworm? We are using that in the ops/containers Dockerfiles. There appear to be other Snyk vulnerabilities popping up that are introduced through trixie, so this should hopefully address a few of those.

Validation

• Pull branch and build the project. Make sure you can go through a test client auth flow
• Run the following after building the project:
  • docker run --rm bb-local:latest dpkg --get-selections | grep image
  • You should see no results
  • If you run that in master, you will see imagemagick returned

What Security Implications Does This PR Have?

Please indicate if this PR does any of the following:

• Adds any new software dependencies
• Modifies any security controls
• Adds new transmission or storage of data
• Any other changes that could possibly affect security?

• Yes, one or more of the above security implications apply. This PR must not be merged without the ISSO or team
  security engineer's approval.

Any Migrations?

• Yes, there are migrations
  • The migrations should be run PRIOR to the code being deployed
  • The migrations should be run AFTER the code is deployed
  • There is a more complicated migration plan (downtime,
    etc)
• No migrations