Timepix streaming

[dylanmcreynolds]

This PR adds the timepix "heatmap streaming" zmq listener.

For the time being, we support two modes for the xps_operator:

• Bassler streaming where our operator code builds heatmaps
• Timepix mode, where upstream code produces heatmaps

Wwe will soon probably remove the bassler/heatmap building code from this repo, but not today.

docker-compose.yml has been updated to make timepix the defult.

This also adds a uv.lock file for development.

This PR does not result in end-to-end processing of timepix. When the timepix code sends a start and stop message, then we will follow up with a PR here to use those to reset counters.

[gabrielgazollalbl]

in schemas.py:

1. maybe it is not clear the difference between

frame_number and shot_num

maybe rename to:

current_frame_number, total_shot_number ?

2. Should we have a validation logic for the fields ?

=====

in websockets.py:

Why removing these lines? Not needed for Timepix?

"shot_mean": convert_to_uint8(message.shot_mean.array),
"shot_std": convert_to_uint8(message.shot_std.array),

=====

[dylanmcreynolds]

For schemas, I agree. Frames were different from shots when using the Bassler camera. With the timepix, it frame_number doesn't actually mean anything. In a future world the beamline may choose to only use the timepix and we cane remove the frame.

I removed a lot of fields from the websockets.py return package because they are no longer needed in the react UI.