Move device connection history to semantic activity storage

[bytemaster-0xff]

Expands the RuntimeData storage seams into the semantic-storage migration for device connectivity.

Connection history:

• DeviceConnectionEvent implements IActivityRecord
• DeviceConnectionEventRepo composes IActivityRecordStore<DeviceConnectionEvent> instead of inheriting TableStorageBase
• Cassandra activity shape partitions by OrganizationId + DeviceId
• existing per-device history API is preserved using opaque provider continuation tokens
• runtime writes populate authoritative organization context from the DeviceRepository
• DI registers CassandraActivityRecordStore<DeviceConnectionEvent>
• no TTL is invented yet; retention remains an explicit policy decision

Device status preparation:

• adds the missing IDeviceStatusChangeRepo.AddDeviceStatusHistoryAsync seam so RuntimeData can forward watchdog history writes server-side
• current status remains mutable and is now targeted at the new IOperationalRecordStore semantic category rather than Mongo/ApplicationData
• immutable status history can follow the Activity Record pattern
• the current Azure repo remains in place until CloudStorage's major refactor settles and the OperationalRecord provider is available

Dependency note: the connection-history branch requires a LagoVista.CloudStorage package containing the semantic Activity Record contracts/provider before it can be merged/published. OperationalRecord provider work is intentionally deferred until the current CloudStorage refactor is complete.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud