fix: Fix SSL Context switching

[pavel-jares-bcm]

Description

There is a use case when a service uses a ZAAS client and onboarding enabler together. The setup of the default SSL context factory could lead to a failing onboarding enabler.

step to reproduce:

1. onboard by enabler (the connection fetched the default SSL context - using to detect if the SSL should be set - see the issue in Jersey)
2. wait for at least 30 seconds - onboarding is working
3. create a ZAAS client and try to call any endpoint (ie. login)
4. onboarding started failing with 403 (default SSL context changed, ZAAS client stopped using client certificate)

The issue happened because of implementation in Jersey, see issue eclipse-ee4j/jersey#5637

• It has started because of PR Lazy synchronized SSL Context initialization in the HttpUrlConnector eclipse-ee4j/jersey#4764 (since 2.34)
• The APIML has upgraded Jersey from version 2.26 at chore: Improve dependency management #2923

Linked to # (issue)
Part of the # (epic)

Type of change

Please delete options that are not relevant.

• fix: Bug fix (non-breaking change which fixes an issue)
• feat: New feature (non-breaking change which adds functionality)
• docs: Change in a documentation
• refactor: Refactor the code
• chore: Chore, repository cleanup, updates the dependencies.
• BREAKING CHANGE or !: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the style guidelines of this project
• PR title conforms to commit message guideline ## Commit Message Structure Guideline
• I have commented my code, particularly in hard-to-understand areas. In JS I did provide JSDoc
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The java tests in the area I was working on leverage @nested annotations
• Any dependent changes have been merged and published in downstream modules

For more details about how should the code look like read the Contributing guideline

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud