Historian Chunk Intervals and Retention Fixes

Improvements

• The historian output takes value_chunk_interval and attribute_chunk_interval, setting how wide a TimescaleDB chunk is for each of its two hypertables, both still defaulting to 168h. An interval applies only when a table is created, so changing it later needs set_chunk_time_interval on the database, and a restart warns when a configured interval no longer matches its table

Fixes

• The historian output now applies compression and retention to every data contract, not only the first one. Existing historian setups are unaffected
• The historian no longer stores timestamp_ms as a tag attribute, which previously wrote one attribute row per data point