Rely on actual unix time instead of timezone specific human-readable one

[marcfedorow]

Describe the idea

Use UNIX time to determine whether the place is open (when the train departs, ...).
Ignore the device's timezone, use the timezone of the region instead.

Expected behaviour

Application correctly defines whether the place is open if the device's time is correct regardless of the device's timezone.

Alternatives you've considered

Manually setting the proper timezone of the according region.

Context

It is somewhat related to #15119; I believe one fix might close both issues.
My case is:

• My device is set to the correct (UNIX) time (say, 1738229100);
• My device's timezone (say, GMT) is different from the time of the region (say, GMT+9 for tme map of the Kansai region, Japan);
• This implies that my device's human-readable time (Thu Jan 30 2025 09:25:00 GMT+0000) is different from the actual time of the location (Thu Jan 30 2025 18:25:00 GMT+0900 (JST));
• Say, there is a place that is open 09:00:00~18:00:00 (JST);
• OsmAnd displays that this place is open because my device's human-readable time is 09:25:00 (not 18:25:00); though this place is actually closed at 1738229100 (UNIX).

This comment suggests guessing timezone by latitude/longitude. I think it is unnecessary because the timezone can be determined through the metadata of the map (region).