Improve IMU data structure for timestamp logging

[WT-MM]

Problem

Hiwonder has a timestamp field we want to access. Also, we want to know the effective frequency of the imu reader (i.e. how often we are receiving new data)

Solution

• Expanded ImuData to include timestamp and effective frequency
• Add new_data counting logic to hiwonder
• Add match case for timestamp frames from hiwonder

Validation

• Manual test steps documented (screenshots, steps, etc.) below:

^^ running cargo run --bin read_hiwonder

Checklist

• I've completed all the documentation steps above (problem, solution, validation).
• I confirm there's no AI slop in this PR.
• I've updated the documentation to reflect my changes.

[Copilot]

Pull Request Overview

This PR expands the IMU data structure to include a timestamp and effective frequency field, while adding logic to parse new timestamp frames from the Hiwonder device and updating dependency versions.

• Expanded ImuData in imu-traits to support timestamps and effective frequency.
• Updated Hiwonder reader to parse and assign timestamp information from device-provided time fields.
• Bumped dependency versions across multiple Cargo.toml files.

Reviewed Changes

Copilot reviewed 13 out of 13 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
imu/imu-traits/src/lib.rs	Expanded ImuData with timestamp and effective_frequency fields.
imu/drivers/hiwonder/src/lib.rs	Added parsing logic for timestamp frames and effective frequency update.
imu/drivers/*/Cargo.toml	Updated version numbers and dependencies accordingly.
imu/bindings/src/lib.rs	Added Python binding for Timestamp.
imu/init.py	Updated module exports with Timestamp.
Cargo.toml	Bumped workspace version.

Comments suppressed due to low confidence (1)

imu/drivers/hiwonder/src/lib.rs:398

• The addition of 1 to the year value may be incorrect because years are not 1-indexed. Verify whether this offset is intentional or if it unintentionally shifts the timestamp year.

year as i32 + 1,

[jingxiangmo]

Found and discussed error with warmup time. Please refer to Scott's implementation: https://github.com/kscalelabs/kos-zbot/blob/master/kos_zbot/imu.py