HIVE-30142: Upgrade develocity extensions for maven 3.10.0 compatibility

[Aggarwal-Raghav]

What changes were proposed in this pull request?

Upgrades the versions of the Develocity extensions in .mvn/extensions.xml:

• develocity-maven-extension is upgraded from 1.22.2 to 2.6.0
• common-custom-user-data-maven-extension is upgraded from 2.0.1 to 2.4.0

Why are the changes needed?

Hypothesis:
The recent release of Apache Maven 3.10.0 introduced changes in Maven resolver which is same as Maven4+ https://maven.apache.org/docs/3.10.0/release-notes.html#new-features-and-improvements

Upgrading develocity extension to latest version is helping with the error.

❯ mvn clean install -DskipTests -Pitests,dist,errorProne
[INFO] Loaded 24022 auto-discovered prefixes for remote repository central (prefixes-central.txt)
[INFO] Scanning for projects...
[INFO] Loaded 24022 auto-discovered prefixes for remote repository central (prefixes-central.txt)
[INFO] Loaded 7 auto-discovered prefixes for remote repository shibboleth (prefixes-shibboleth.txt)
[INFO] Loaded 24022 auto-discovered prefixes for remote repository central (prefixes-central.txt)
[ERROR] Internal error in Develocity Maven extension: DevelocityLifecycleManager afterProjectsRead
com.gradle.maven.common.logging.DevelocityException: Internal error in Develocity Maven extension: DevelocityLifecycleManager afterProjectsRead
    at com.gradle.maven.common.logging.DevelocityException.a (SourceFile:31)
    at com.gradle.maven.internal.DevelocityLifecycleManager.afterProjectsRead (SourceFile:277)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:229)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:179)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:1017)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:299)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:219)
    at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:103)
    at java.lang.reflect.Method.invoke (Method.java:580)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:362)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)
Caused by: com.google.inject.ProvisionException: Unable to provision, see the following errors:

1) [Guice/NullInjectedIntoNonNullable]: null returned by binding at LocatorWiring
 but the 2nd parameter pluginDescriptorCache of com.gradle.maven.internal.b.<init>(SourceFile:34) is not @Nullable
  at LocatorWiring
  at com.gradle.maven.internal.b.<init>(SourceFile:34)
      \_ for 2nd parameter pluginDescriptorCache
  while locating com.gradle.maven.internal.b
  while locating com.gradle.develocity.agent.maven.a.a.a annotated with @Named("com.gradle.maven.internal.b")

Learn more:
  https://github.com/google/guice/wiki/NULL_INJECTED_INTO_NON_NULLABLE

Does this PR introduce any user-facing change?

NO

How was this patch tested?

Will see CI output

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud