Add connect/read/write timeouts to Config

[goenning]

Signed-off-by: goenning me@goenning.net

Motivation

closes #969

Solution

• Basically adding new timeout fields for connect/read/write for more granular control.
• Deprecates the existing timeout field.
• connect_timeout to 30s by default, which aligns with client-go and Go's defaultTransporter:
  • https://github.com/kubernetes/client-go/blob/3e9c4b4f174fc7e102dbb53fd39e3714ec70665a/transport/cache.go#L98
  • https://github.com/golang/go/blob/master/src/net/http/transport.go#L45
• write_timeout is set to None by default. It doesn't seem like client-go and Go's http.DefaultClient have a default timeout for it either. And kube-rs didn't have a default before either, so I thought it might be better to not change this.
• read_timeout stays at 295s by default
• DEFAULT_TIMEOUT and the timeout property can be removed later.

Note 1: I'm new to Rust, I might have made mistakes :)

[codecov-commenter]

Codecov Report

Merging #971 (fb7fe9f) into master (fb695bc) will decrease coverage by 0.04%.
The diff coverage is 54.54%.

@@            Coverage Diff             @@
##           master     #971      +/-   ##
==========================================
- Coverage   72.41%   72.37%   -0.05%     
==========================================
  Files          64       64              
  Lines        4430     4438       +8     
==========================================
+ Hits         3208     3212       +4     
- Misses       1222     1226       +4     

Impacted Files	Coverage Δ
kube-client/src/config/mod.rs	48.80% <37.50%> (-1.20%)	⬇️
kube-client/src/client/builder.rs	70.90% <100.00%> (ø)
kube-runtime/src/wait.rs	71.69% <0.00%> (+1.88%)	⬆️