[DOP-23590] Change log level for py4j logs

[dolfinus]

Change Summary

Avoid worker logs from being flooded by p4j:

{"processName": "ForkPoolWorker-17", "process": 1964, "threadName": "Thread-9 (run)", "thread": 140076660934336, "name": "py4j.clientserver", "lineno": 575, "levelname": "INFO", "message": "Received command c on object id p1", "correlation_id": "-", "timestamp": "2025-01-28T12:27:19.166390+00:00"}
{"processName": "ForkPoolWorker-17", "process": 1964, "threadName": "Thread-9 (run)", "thread": 140076660934336, "name": "py4j.clientserver", "lineno": 575, "levelname": "INFO", "message": "Received command c on object id p1", "correlation_id": "-", "timestamp": "2025-01-28T12:27:19.169981+00:00"}
{"processName": "ForkPoolWorker-17", "process": 1964, "threadName": "Thread-9 (run)", "thread": 140076660934336, "name": "py4j.clientserver", "lineno": 575, "levelname": "INFO", "message": "Received command c on object id p1", "correlation_id": "-", "timestamp": "2025-01-28T12:27:19.173491+00:00"}

Related issue number

Checklist

• Commit message and PR title is comprehensive
• Keep the change as small as possible
• Unit and integration tests for the changes exist
• Tests pass on CI and coverage does not decrease
• Documentation reflects the changes where applicable
• docs/changelog/next_release/<pull request or issue id>.<change type>.rst file added describing change
  (see CONTRIBUTING.rst for details.)
• My PR is ready to review.