Why is DATA returned from server has a DAteTimeOffset into local zone, even though we use UTC?

```
{
"Gdid": "0:0:1",
"Id": "entrp.gdid@XXXXXXXXXXXXX::000000000000000000000001",
"Mnemonic": "EN-XXXXXXXXXXX",
"Caption": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"DataVersion":
{
"G_Version": "0:0:1",
"Utc": "2021-08-25T18:00:24-04:00", <--------------????????????????
"Origin": "A",
"Actor": "id@idp::XXXXXXXXXXXXXXXX",
"State": "Created"
},
"StartUtc": "2021-08-25T18:03:49-04:00", <---------- ???????????
"Properties": "{\"r\":{}}",
"LevelConfig": "{\"r\":{\"a\":\"1\",\"b\":\"2\"}}",
"EffectiveConfig": "{\"r\":{\"a\":\"1\",\"b\":\"2\"}}"
}
```

Start by reproducing the server response shown in the issue and inspect how the Utc and StartUtc DateTimeOffset values are produced and serialized. Trace the relevant date-time handling from the returned data to the response, then document or correct the behavior so the result consistently matches the configured UTC expectation.

Written by the indexing model from the issue text.