UFAL/Inccorect time zone UTC

[Paurikova2]

Problem

The time zone problem is more complex than we thought.

Are we sure that we want to display the current (local) time zone and not Greenwich (UTC) time?
If yes, then changes will need to be made both on the backend and on the frontend, because there are incorrect dates stored or shown in the backend (e.g. provenance, metadata, etc.), as well as inconsistencies in how dates are displayed on the frontend (e.g. process start/end dates, etc.).

My tried:
https://github.com/dataquest-dev/dspace-angular/compare/dtq-dev...dataquest-dev:dspace-angular:ufal/time-zone?expand=1
https://github.com/dataquest-dev/DSpace/compare/dtq-dev...dataquest-dev:DSpace:ufal/time-zone?expand=1

[Paurikova2]

We are intentionally keeping UTC as the system-wide standard because it provides a single, unambiguous time reference across backend services, APIs, provenance, and metadata, which is critical for data consistency and auditability. Supporting localized timezones is not a simple display change — it requires coordinated backend, frontend, and historical data handling changes, with a real risk of introducing timestamp shifts or inconsistencies. Given the scope and risk, this is a separate technical initiative and not in scope compared to current priorities, while UTC-based timestamps remain correct and reliable.