chore(deps): update okhttp to 5.3.2

[klopfdreh]

Description

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change
• Chore (non-breaking change which doesn't affect codebase;
  test, version modification, documentation, etc.)

Checklist

• Code contributed by me aligns with current project license: Apache 2.0
• I Added CHANGELOG entry regarding this change
• I have implemented unit tests to cover my changes
• I have added/updated the javadocs and other documentation accordingly
• No new bugs, code smells, etc. in SonarCloud report
• I tested my code in Kubernetes
• I tested my code in OpenShift

Issues Ref: #7421

[klopfdreh]

• E2E Tests / BuildWithoutTests failed because package okhttp3 does not exist
• Java 17 Maven (pull_request) failed because of kubernetes-httpclient-jdk which was not affected by the change
• Java 21 Maven (pull_request) failed because of the same cause like E2E Tests / BuildWithoutTests
• Java 11 Maven (pull_request) failed because of the same cause like E2E Tests / BuildWithoutTests

I added okhttp-jvm manually to kuberntes-examples as there was no bom import for okhttp - a new feature of version 5.x is that the environment is discovered automatically and okhttp-jvm or okhttp-android is added as dependency. This is somehow not working in the github action. But when I used the workaround described in the issue okhttp-jvm is pulled like it should be.

[klopfdreh]

All right - all checks passed. 💚 😃

[ash-thakur-rh]

Hi @klopfdreh , Thank you for the PR! We'll have a look into it soon and will try to include your changes.