update kubernetes java client to 19.0.0 and docker-java to 3.3.4

[janjwerner-confluent]

Description:

Update of direct dependencies:

• kubernetes java-client to 19.0.0
• docker-java-bom to 3.3.4

In order to update transitive dependencies:

• okio to 3.6.0
• bcjava to 1.76

To address CVES:

• CVE-2023-3635 in okio
• CVE-2023-33201 in bcjava

This PR has:

• been self-reviewed.
  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
• added documentation for new or modified features or behaviors.
• a release note entry in the PR description.
• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
• added or updated version, license, or notice information in licenses.yaml
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• added integration tests.
• been tested in a test Druid cluster.

[janjwerner]

The integration failure caused by the change of line 68:
re-reviewing the API docs
Caused by: org.apache.druid.java.util.common.RE: Failed to patch pod[default/druid-tiny-cluster-historicals-0], code[422], error[{ "kind": "Status", "apiVersion": "v1", "metadata": {}, "status": "Failure", "message": "PatchOptions.meta.k8s.io \"\" is invalid: force: Forbidden: may not be specified for non-apply patch", "reason": "Invalid", "details": { "group": "meta.k8s.io", "kind": "PatchOptions", "causes": [ { "reason": "FieldValueForbidden", "message": "Forbidden: may not be specified for non-apply patch", "field": "force" } ] },

[janjwerner-confluent]

Given that the arguments are optional, I replaced the specific values with nulls. This let me stand up the cluster, now testing the change using ci/cd.