Fixes #57515 - Fix test_async_write_logs_should_execute_successfully test

[hwang-cadent]

Description

This PR fixes the broken test test_async_write_logs_should_execute_successfully() in the KubernetesPodOperator test suite. The test was incorrectly implemented and was not properly testing the async log writing functionality.

Changes

• Added @patch(KUB_OP_PATH.format("client")) decorator to properly mock self.client.read_namespaced_pod_log() which is the actual method used by _write_logs()
• Fixed mock setup to use mocked_client.read_namespaced_pod_log instead of incorrectly mocking mock_manager.read_pod_logs (which is never called)
• Fixed mock return value to return an iterable of bytes: [test_logs.encode("utf-8")] as expected by the implementation
• Added mock_manager.await_pod_completion.return_value for proper test flow
• Fixed assertions to verify actual log output using caplog instead of a meaningless string assertion
• Fixed get_logs=False assertion to check mocked_client.read_namespaced_pod_log.assert_not_called() instead of the incorrect pod_manager.read_pod_logs check

Root Cause

The test had three main issues:

1. Wrong mock target: It mocked pod_manager.read_pod_logs but _write_logs() actually calls self.client.read_namespaced_pod_log() directly
2. Incorrect assertion: The assertion assert f"Container logs: {test_logs}" always passes (it's just checking if a string exists, not if it was logged)
3. Wrong verification for get_logs=False: It checked pod_manager.read_pod_logs which is never called by _write_logs()

Testing

• Both parameterized test cases now pass:
  • test_async_write_logs_should_execute_successfully[True] ✅
  • test_async_write_logs_should_execute_successfully[False] ✅
• All existing tests continue to pass

Type of Change

• Bug fix (non-breaking change which fixes an issue)

Fixes #57515

[jscheffl]

FInally now some static checks fail - can you run our pre-commit checks via prek (or ruff in this case) to fix code and push fixes?

[hwang-cadent]

FInally now some static checks fail - can you run our pre-commit checks via prek (or ruff in this case) to fix code and push fixes?

Applied ruff formatting fixes: removed unused imports and formatted function parameters. All prek checks pass. Thanks!

[jscheffl]

Looks good! LGTM when CI turns green!