Remove deprecated joda-time and migrate to java.time

[Turribeach]

We had some of our scenarios execute at the wrong time. Long story short Dataiku is using a very old third party time zone library (joda-time v2.9.5) with outdated DST data. This is the case even on DSS v12.2.3 which still runs on joda-time v2.9.5. Furthermore this version of joda-time is ancient as it was released in 3-Nov-2016 (see https://www.joda.org/joda-time/changes-report.html) so it's about to be 7 years old. While time zones and DST arrangements don't change that often there are usually 3-4 updates a year (see https://mm.icann.org/pipermail/tz-announce/ which is where joda-time sources it's time zone data).

Finally my research also unveiled that the joda-time library has been deprecated since Java SE 8 (released in 2014) as even the joda-time developers recommend using the native java.time (see https://www.joda.org/joda-time/):

Note that from Java SE 8 onwards, users are asked to migrate to java.time (JSR-310) - a core part of the JDK which replaces this project.

Moving to java.time will not only allow DSS admins to have up-to-date time zone information but also self update OpenJDKs time zone data when required completely eliminating the time zone out-of-date data issue.

So in summary this idea is to remove the deprecated joda-time Java third party library from DSS and migrate to java.time. Thanks

[yashpuranik]

We have also seen scenarios executing at unexpected times! I strongly support this idea!

[yashpuranik]

We have also seen scenarios executing at unexpected times! I strongly support this idea!