os: Upgrade python3-libcamera to fix issue on bookworm

[sonnyp]

See raspberrypi/picamera2#1229 (comment)

Artifact image to test: https://github.com/PlanktoScope/PlanktoScope/actions/workflows/build-os-bookworm-dx.yml?query=branch%3Afix-bookworm-zoom

[ethanjli]

Looks good to me, but maybe https://github.com/PlanktoScope/PlanktoScope/pull/551/files#r2024924080 (which was a reply-comment I added before starting my review, oops!) is also a possible change suggestion.

[chevreuill3000]

This solved the issue on my end. I approve this work 🥇

As you can see the cute daphnia below which illustrate the fact that we do not subsample the stream anymore :

[chevreuill3000]

good job here

[ethanjli]

Hmm, it looks like the bullseye builds fail when we version-pin. Here are the options I've thought of:

1. follow the pattern set in https://github.com/PlanktoScope/PlanktoScope/blob/790290f28b8b47c08bfaa64fe1499ba75468c20e/software/distro/setup/base-os/platform-hardware/config.sh#L29-L30 for conditional execution in bullseye vs. bookworm.
2. go back to having no version-pinning for python3-libcamera.
3. merge os: Switch to bookworm, drop bullseye support #543 first (or rebase this PR on os: Switch to bookworm, drop bullseye support #543), merge this PR, and just accept that bullseye builds will fail until we implement option 1 or option 2 in a future PR.

I have a weak preference for option 1.

[sonnyp]

@ethanjli I will leave as is for simplicity and added a todo to revert this in PlanktoScope/device-backend#78

[ethanjli]

As discussed in the 2025-04-09 core team meeting, after finishing+merging #543 I will make a follow-up PR for version-pinning the picamera2 apt package - and the follow-up PR will not include any special bookworm-specific version guards for version-pinning the apt picamera2 package. The implication is that the OS setup scripts will no longer work on bullseye - see #543 (comment) for more context.