This makes no sense anymore, secondary will send this after registration, so we need to decide earlier based on the device type.
This change is not backward compatible but this flow hasn't been launched yet so we not breaking anything.
Depends on D13965
Note that we use RFC 3339 string for ItemID while the ATTR_TIMESTAMP uses milliseconds number. Generally I use the former everywhere (simpler parsing without NaiveDateTime conversions) but I thought the latter is easier for DDB to sort by (it's used only as index sorting key and not read anywhere else)