Fix CustomJacksonDateFormatTest

Context

• The test CustomJacksonDateFormatTest failed with:

  org.jboss.shrinkwrap.resolver.api.NoResolvedResultException: Unable to collect/resolve dependency tree for a resolution due to: The following artifacts could not be resolved: org.glassfish.jersey.core:jersey-common:jar:2.25.1, org.glassfish.jersey.bundles.repackaged:jersey-guava:jar:2.25.1, org.javassist:javassist:jar:3.20.0-GA, org.glassfish.jersey.core:jersey-server:jar:2.25.1: Could not transfer artifact org.glassfish.jersey.core:jersey-common:jar:2.25.1 from/to camunda-nexus (https://camunda.jfrog.io/artifactory/internal/): Error transferring file: Server returned HTTP response code: 400 for URL: https://jfrog-prod-euc1-shared-frankfurt-main.s3.amazonaws.com/aol-camunda/filestore/24/2438ce68d4907046095ab54aa83a6092951b4bbb?x-jf-traceId=13ab888b4731be97&response-content-disposition=attachment%3Bfilename%3D%22jersey-common-2.25.1.jar%22&response-content-type=application%2Fjava-archive&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20220104T123817Z&X-Amz-SignedHeaders=host&X-Amz-Expires=60&X-Amz-Credential=AKIASG3IHPL65SRFOM76%2F20220104%2Feu-central-1%2Fs3%2Faws4_request&X-Amz-Signature=69028eff0696bbfac260aa96ecc4139fba21c5d5087c2a100fe54d70aa97944b from https://camunda.jfrog.io/artifactory/internal/org/glassfish/jersey/core/jersey-common/2.25.1/jersey-common-2.25.1.jar, caused by: Server returned HTTP response code: 400 for URL: https://jfrog-prod-euc1-shared-frankfurt-main.s3.amazonaws.com/aol-camunda/filestore/24/2438ce68d4907046095ab54aa83a6092951b4bbb?x-jf-traceId=13ab888b4731be97&response-content-disposition=attachment%3Bfilename%3D%22jersey-common-2.25.1.jar%22&response-content-type=application%2Fjava-archive&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20220104T123817Z&X-Amz-SignedHeaders=host&X-Amz-Expires=60&X-Amz-Credential=AKIASG3IHPL65SRFOM76%2F20220104%2Feu-central-1%2Fs3%2Faws4_request&X-Amz-Signature=69028eff0696bbfac260aa96ecc4139fba21c5d5087c2a100fe54d70aa97944b
  

• We have the hypothesis that this is related to the Maven 3.2 internal HTTP Client that cannot handle TLS 1.2 connections
• After reintroducing the Nexus CI Cache, the test stopped failing

Acceptance Criteria (Required on creation):

The test doesn't fail anymore.

Hints (optional):

-