Allow users to display local time in profile

[JakobDev]

Implements https://codeberg.org/forgejo/forgejo/issues/1089

This allows users to set their timezone in the profile settings, so their local time will be displayed on the profile.

Where does the data came from?
From this CSV

Why use the CSV instead of the built-in timezone support of Go?

1. Go don't provide a function to list all available timeszones. There are workaround to this, but they are just not more than workarounds.
2. Go uses the timezone information from the system. You can compile timezone iformation in the binary, but Go still prefers the system timezones. by using the CSV we can be sure every Gitea instance uses the same information by default.
3. Admins can easily update the timezones if needed

Screenshoots:

As usual, the migration will be added when everything reviewed

[puni9869]

Just a thought and question.

Can't we do it in simple js.
Getting the local time zone and set the UTC to local.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/getTimezoneOffset

[JakobDev]

If we use JS, we can't return the current time with the API. We also can't be sure every users sees the same time. Maybe a timezone changes e.g daylight saving time. In this case, the users will eventually see different times on different devices, depending how up to date it is. Also some people want to use at least JS as possible.

[puni9869]

Also some people want to use at least JS as possible.

Include me that,

I understood your solution. Give me today's time to review this change. Will share my findings.

[delvh]

For anyone wondering, this file hardcodes any timezone change from 1893 to 2499.
Hmm… How much extra strain is that on any instance?
I can't imagine it to be small, my current estimate is something like 7MB.
Is my calculation correct?

[delvh]

Do we want that much "bloat"?

[puni9869]

Is that .gz and still 7mb.

[JakobDev]

Without gzip, the file is currently 6.05 MB, which gzip it's 844 KB. I will rewrite 5the Code to use a gziped file.

[puni9869]

IMO gzip is fine. I am okay with that.

[JakobDev]

The CSV is now compressed

[puni9869]

Thanks @JakobDev I have reviewed the half Pr, Need todays'time more.

[JakobDev]

I was able to reduce the size drastically. The CSV now only contains the info from 5 years ago until 30 years in the future. It also only includes the needed columns. We are now at 45KB.