`Microsoft.Network/dnsResolvers` API modifies RFC3339 time request values set in `tags`

When creating a DNS resolver via following request:

PUT https://management.azure.com/subscriptions/xxxx/resourceGroups/acctestRG-ACRTask-211215101546495724/providers/Microsoft.Network/dnsResolvers/ababab?api-version=2022-07-01

```
{
...
"tags": {
"time": "2023-07-05T13:06:05Z"
}
}
```

After created, I do a GET on the resource and the response returned me:

```
{
...
"tags": {
"time": "7/5/2023 1:06:05 PM"
}
}
```

The expected behavior is that RP team guarantees the round trip consistency and keep the value as what users have specified, i.e. "2023-07-05T13:06:05Z".

This behavior applies not only to the dns resolver, also applies to the dns resolver forwarding ruleset, etc.

## Reference

https://github.com/hashicorp/terraform-provider-azurerm/issues/22408

Review the documented Microsoft.Network/dnsResolvers and related forwarding-ruleset API behavior, comparing the PUT tag value with the subsequent GET response. Check the referenced Terraform issue for context; done would require an agreed resolution for preserving RFC3339 tag values, but no repository file or test is identified here.

Written by the indexing model from the issue text.