util: Don't use TZ offset for media Premiere Date

[fice-t]

I'm fairly new to Java/Kotlin/Android, so I'm not sure if this approach is the best, or if it should be used in other instances (such as in TimeUtils). It at least appears to fix the linked issue.

Is it reasonable to cut out usage of Date and stick with LocalDateTime, here and perhaps in TimeUtils?

Also: the "Premiere" date for TV seasons inside InfoLayoutHelper::addDate is in UTC, but the "Premiere"/"Born" date for actors is... odd. For example, in UTC-6: 1950-01-01T06:00, and UTC+3: 1950-01-01T15:00. Is this coming from the server, or was it changed in the client? Perhaps it acts oddly when the client is set to a different TZ than the server?

Changes

TimeUtils.getDate internally calls Date.format, which translates the UTC timestamp into local TZ timestamp. If a user is in a TZ with negative offset, then the Premiere Date will be presented as a day earlier.

Example with TZ of UTC-6:

item.getPremiereDate() => 2023-12-09T00:00
TimeUtils.getDate(item.getPremiereDate()) => Sat Dec 08 18:00:00 CST 2023

Issues

Fixes #3190.

[nielsvanvelzen]

The old apiclient used Date, everything with the new SDK uses java.time. For conversion we have the ModelCompat helpers that will convert Date->java.time. I thought I fixed most of the timezone issues but apparently not 😄.