Update dependencies with critical CVEs

[tronda]

Which problem is this PR solving?

• Spark Dependencies job has dependencies towards Java libraries with critical CVE associated with them. This PR will update those dependencies
• The Spark Dependencies job does not work with OpenSearch with the given version of the ElasticSearch dependency. By upgrading the ElasticSearch depdency, this Spark job is able to use OpenSearch as the storage backend.

Description of the changes

• Override the dependencies in the maven's pom files
• Update ElasticSearch Java library

How was this change tested?

• We have created our custom docker build of this Spark job and ran it internally for a long time with OpenSearch as the storage.
• Also verified that our internal security scanner removed those critical CVEs from the deployment.
• The tests are failing in this repo so I was not able to run the tests (no new tests added)

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully

[recena]

Any news here?

[yurishkuro]

superseded by #135