Add transducer tracking data to session definition

[ebrahimebrahim]

The outcome of transducer tracking should be saved to sessions as a special thing, not just as an update to the “current transducer transform” and a tracking approval flag.

So the goal here is to replace the current transducer tracking approval flag in Session by a richer data structure which is a list of transducer tracking results. Each transducer tracking result consists of a photoscan ID and two transforms (the outputs of the tracking algorithm), and also an approval state for that transducer tracking result.

Depends on #177

---

Traceability Information:

• Issue: OpenLIFU-python#182
• SOFTREQ: SlicerOpenLIFU#35
• Comment: This issue is related to the requirements defined in SlicerOpenLIFU#35.

This information was populated automatically by a script on 2025-06-09T18:02:09Z.

[sadhana-r]

Replace transducer_tracking_approved attribute with transducer_tracking results which is an Optional List of transducer tracking result. Each transducer tracking result (dataclass) will contain 'photoscan_id' (str), 'photoscan_to_mri_transform' (ArrayTransform), 'transducer_to_photoscan_transform' (ArrayTransform) and 'transducer_tracking_approved' (bool). For now, we will keep the array_transform attribute which keeps track of the 'current_transducer_transform'. [[Need to confirm the direction of the transform in the registration algorithm]].