[SEDONA-322] Fix unstable maven build on GitHub Actions

[Kontinuation]

Did you read the Contributor Guide?

• Yes, I have read Contributor Rules and Contributor Development Guide

Is this PR related to a JIRA ticket?

• Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-322. The PR name follows the format [SEDONA-XXX] my subject.

What changes were proposed in this PR?

The CI for Scala/Java build fails frequently. The failure was triggered by a failed maven artifact download:

Error:  Plugin org.apache.maven.plugins:maven-shade-plugin:3.4.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-shade-plugin:jar:3.4.1: Could not transfer artifact org.apache.maven.plugins:maven-shade-plugin:pom:3.4.1 from/to central (https://repo.maven.apache.org/maven2): transfer failed for https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-shade-plugin/3.4.1/maven-shade-plugin-3.4.1.pom: Connection timed out (Read failed) -> [Help 1]

This is caused by a networking problem of Microsoft Azure. Please refer to actions/runner-images#1499 for details. This patch workaround the networking problem by discarding long-living TCP connections.

How was this patch tested?

Trigger the CI multiple times to see if the problem persists.

Did this PR include necessary documentation updates?

• No, this PR does not affect any public API so no need to change the docs.