Upgrade to okhttp4

[vmuzikar]

The upgrade to okhttp4 performed in the SDK doesn't seem to be reflected in the Quarkus extension, it appears to be still using okhttp 3.14.9.

The upgrade is critical as it fixes a security vulnerability.

[metacosm]

The Quarkus extension uses whatever version of the client is provided by Quarkus, so this issue should be brought up at the Quarkus level.

[metacosm]

We're not using the okhttp client anymore (this was a transitive dependency of the Fabric8 kubernetes client). This might still be pulled if you're using the Fabric8 client's mockserver in your test but that should only be pulled with a test scope anyway.