[Bug]: Evaluate Error when The time is not valid in the current time zone. (clock is adjusted forward) -> context Azure Blob Storage

Describe the issue

There is a possibility that files(blobs) cannot be imported from Azure Blob Storage because the Created or Modified At timestamp cannot be evaluated.

The timestamps of the file/blobs are returned in the API using UTC time. The timestamps (created, modified) returned by the API are converted to DateTime as text using Evaluate.
Evaluate throws an error if the time does not exist in the region. (Error Message: The time '30.03.2025 02:00:01' is not valid in the current time zone. For example, when the clock is adjusted forward, any time in the period that is skipped is invalid.)
In my opinion, this can only happen in the context of the switch to summer saving time (e.g., from 2:00 a.m. to 3:00 a.m.). All times between 2 and 3 then do not exist.

However, this time does exist in UTC time, and it is possible to create a file in Azure Blob Storage during this time. Due to the Evaludate error, however, these files cannot be imported.

In my opinion, the Evaluate function should offer the option of performing a UTC validation. After all, the time entered is actually validated.

Expected behavior

Blobs from Azure Blob Storage that were created during the time change should be able to be imported.

Evaluate should not throw an error if it is a Validate UTC input. Perhaps a UTC time parameter is needed.

Steps to reproduce

Create a file in Azure Blob Storage during the time shift in your region and try to import it.

Additional context

No response

I will provide a fix for a bug

• I will provide a fix for a bug

Start by tracing the Evaluate conversion used when importing Created or Modified At timestamps from Azure Blob Storage, focusing on the UTC values described in the report. Reproduce the daylight-saving transition case and verify that blobs created during the skipped local-time period can be imported without the invalid-time error.