Fix/time badge still wrong

[Bima42]

What is this PR about?

Problem:
The TimeBadge component was always displaying UTC+00:00 regardless of the actual server timezone.

The client was calculating the offset by converting dates to strings using toLocaleString, then parsing those strings back into Date objects. When JavaScript parses a date string like "1/15/2025, 9:00:00 AM" with new Date(), it interprets it in the browser's local timezone, not the intended timezone. Both dates ended up in the same timezone, so the offset was always zero.

Fix:
I moved the offset calculation to the server side. The server now returns the offset along with the timezone and time. We use Intl.DateTimeFormat.

Extracted the offset calculation logic to utils/time.ts as getUtcOffset(timeZone) with comprehensive tests covering various timezones including edge cases like half-hour offsets (India UTC+05:30), invalid inputs, and the UTC special case.

Issues related (if applicable)

closes #3328

[Siumauricio]

I don't know what's wrong here? you need to setup the timezone here https://docs.dokploy.com/docs/core/manual-installation#setup-dokploy-timezone

[Bima42]

You're right, my bad for not checking the docs first. Closing this now, sorry for the noise!