Kubernetes worker use none for _request_timeout

[jeanluciano]

Overrides the default total of the ClientTimeout that gets passed to list_namespace_job. This avoids timeouts where no event gets sent for more than the default duration of ClientTimeout ,300s.

Checklist

• This pull request references any related issue by including "closes <link to issue>"
  • If no issue exists and your change is not a small fix, please create an issue first.
• If this pull request adds new functionality, it includes unit tests that cover the changes
• If this pull request removes docs files, it includes redirect settings in mint.json.
• If this pull request adds functions or classes, it includes helpful docstrings.

[zzstoatzz]

moving to draft for now until we can articulate the need for this given #15744

cc @kevingrismore

[kevingrismore]

We should be ok removing all the ClientTimeout instances we're passing to _request_timeout with the bumped dependency. I would verify by doing the following:
On the updated async k8s package and all ClientTimeouts removed,

• Try to start a flow run with an impossibly large CPU request and a job start timeout of 10+ minutes. Ensure the timeout is enforced as intended rather than the connection dropping
• Run a flow that doesn't log for 10+ minutes and ensure the connection doesn't drop