Analysis Sub-system

We should add a simple **Analysis** sub-system to CAMS (note that such an analysis sub-system is part of the [original CARP Core architecture](https://github.com/cph-cachet/carp.core-kotlin?tab=readme-ov-file#architecture)).

Use cases include:

* Aggregating step counts over 24 hours, i.e., pr. day
* Feature extraction on IMU (acc, gyro, mag) [x,y,z] data
* Calculating mobility features, e.g., homestay and location entropy
* Anonymizing data (note that anonymization of individual measurements is currently handled by the `Transformer` concept in CAMS)
* Calculating a risk score based on one or more surveys (like the color-coding in the [DiaFocus](https://carp.cachet.dk/diafocus/) app)
* Simple human activity recognition (HAR), e.g. via [flutter_litert](https://pub.dev/packages/flutter_litert)

A domain model should specify:

* **WHEN** to do the analysis (e.g., once pr. day (step counts) or after a set of survey have been filled in (DiaFocus))
* **WHAT** the analysis consists of (e.g., feature extraction on IMU data)
* what **DATA** to use (e.g., a list of IMU (x,y,z) data)

**Note** – this looks a lot like the `Trigger-Task-Measure` construct of a `StudyProtocol`