Inconsistency in `DatasetVersionInfo` model? (Date vs string)

I noticed that in the DatasetVersionInfo model, the timestamps use inconsistent types:

https://github.com/IQSS/dataverse-client-javascript/blob/0043dddf5e7d9358d0dcac176cb8c0f325aab78b/src/datasets/domain/models/Dataset.ts#L25-L32

releaseTime and createTime are represented as Date objects, while lastUpdateTime is represented as an ISO 8601 string and not transformed into a Date object:

https://github.com/IQSS/dataverse-client-javascript/blob/0043dddf5e7d9358d0dcac176cb8c0f325aab78b/src/datasets/infra/repositories/transformers/datasetTransformers.ts#L237-L239

The return values from the Dataverse API for retrieving a dataset version are all consistently ISO 8601 strings:

I was wondering what the reason for this is, or whether this inconsistency should be cleaned up? (If so, I'd be open to opening a PR for that)

src/datasets/domain/models/Dataset.ts にある参照先の DatasetVersionInfo 定義と、src/datasets/infra/repositories/transformers/datasetTransformers.ts にある変換処理から始めます。releaseTime、createTime、lastUpdateTime が Dataverse API のレスポンスと比較してどのように表現されているかを確認します。完了の条件は、モデルと transformer が3つすべてのフィールドに対して、意図的で一貫したタイムスタンプ表現を使用していることです。