Update joda dependency to latest 2.10.10 (elastic#72052)

Latest JDKs are shipping with timezone data 2021a which is also included
in latest joda. In order to have the timezone information consistent in
both joda and java.time joda dependnecy has to be updated

closes elastic#72028

Author: pgomulka

buildSrc/version.properties

@@ -19,7 +19,7 @@ slf4j             = 1.6.2
 jna               = 5.5.0
 
 netty             = 4.1.32.Final
-joda              = 2.10.1
+joda              = 2.10.10
 
 # when updating this version, you need to ensure compatibility with:
 #  - plugins/ingest-attachment (transitive dependency, check the upstream POM)

server/licenses/joda-time-2.10.10.jar.sha1

@@ -0,0 +1 @@
+29e8126e31f41e5c12b9fe3a7eb02e704c47d70b

server/src/test/java/org/elasticsearch/common/time/DateUtilsTests.java

@@ -31,11 +31,19 @@
 import static org.hamcrest.Matchers.equalTo;
 
 public class DateUtilsTests extends ESTestCase {
+    // list of ignored timezones.
+    // These should be cleaned up when all tested jdks (oracle, adoptopenjdk, openjdk etc) have the timezone db included
+    // see when a timezone was included in jdk version here https://www.oracle.com/java/technologies/tzdata-versions.html
     private static final Set<String> IGNORE = new HashSet<>(Arrays.asList(
         "Eire", "Europe/Dublin" // dublin timezone in joda does not account for DST
+        "Eire", "Europe/Dublin", // dublin timezone in joda does not account for DST
+        "Asia/Qostanay", // part of tzdata2018h
+        "America/Godthab", // part of tzdata2020a (maps to America/Nuuk)
+        "America/Nuuk"// part of tzdata2020a
     ));
-    
+
     @AwaitsFix(bugUrl = "https://github.com/elastic/elasticsearch/issues/72028")
+
     public void testTimezoneIds() {
         assertNull(DateUtils.dateTimeZoneToZoneId(null));
         assertNull(DateUtils.zoneIdToDateTimeZone(null));

x-pack/plugin/sql/sql-action/licenses/joda-time-2.10.10.jar.sha1

@@ -0,0 +1 @@
+29e8126e31f41e5c12b9fe3a7eb02e704c47d70b