fix: disable timeout for liveness probe in k8s and keep only k8s timeout

[alaeddine-13]

As an executor is increasingly stressed by load, the health check latency is affected.
It may eventually exceed the default 1 second timeout and therefore, an Executor might be killed by k8s.
This PR disables the ping timeout in liveness probes, keeping just the k8s timeout

[codecov]

Codecov Report

Merging #5594 (c96f5a2) into master (89e9286) will increase coverage by 1.29%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5594      +/-   ##
==========================================
+ Coverage   86.68%   87.98%   +1.29%     
==========================================
  Files         124      124              
  Lines        9939    10048     +109     
==========================================
+ Hits         8616     8841     +225     
+ Misses       1323     1207     -116     

Flag	Coverage Δ
jina	87.98% <ø> (+1.29%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
jina/serve/runtimes/head/request_handling.py	90.78% <0.00%> (-3.33%)	⬇️
jina/serve/streamer.py	93.33% <0.00%> (-3.28%)	⬇️
jina/serve/runtimes/asyncio.py	85.82% <0.00%> (-0.90%)	⬇️
jina/serve/runtimes/worker/__init__.py	95.74% <0.00%> (+0.03%)	⬆️
jina/serve/runtimes/gateway/__init__.py	98.36% <0.00%> (+0.08%)	⬆️
jina/serve/runtimes/head/__init__.py	97.85% <0.00%> (+0.11%)	⬆️
jina/checker.py	85.71% <0.00%> (+0.34%)	⬆️
jina/jaml/__init__.py	95.00% <0.00%> (+0.35%)	⬆️
jina/orchestrate/deployments/config/k8s.py	100.00% <0.00%> (+0.61%)	⬆️
jina/orchestrate/deployments/__init__.py	89.77% <0.00%> (+0.62%)	⬆️
... and 13 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[JoanFM]

Can u add a test that can simulate what we were observing? putting time sleeps and overcharging should be good