chore!: update kube-rs dependencies from 1.1 to 3.1

[cratelyn]

 # Cargo.toml
-k8s-openapi = { version = "0.25", default-features = false }
+k8s-openapi = { version = "0.27", default-features = false }

-kube-client = { version = ">=1.1.0,<1.2.0", default-features = false }
-kube-core = { version = ">=1.1.0,<1.2.0", default-features = false }
-kube-runtime = { version = ">=1.1.0,<1.2.0", default-features = false }
-kube = { version = ">=1.1.0,<1.2.0", default-features = false }
+kube-client = { version = "3.1", default-features = false }
+kube-core = { version = "3.1", default-features = false }
+kube-runtime = { version = "3.1", default-features = false }
+kube = { version = "3.1", default-features = false }

Signed-off-by: katelyn martin kate@buoyant.io

[cratelyn]

test failures look like this:

     thread 'exclusive' panicked at examples/tests/lease.rs:36:5:
    assertion `left == right` failed
      left: 2026-07-09T21:15:44.272047521Z
     right: 2026-07-09T21:15:44.272047Z

    thread 'expires' panicked at examples/tests/lease.rs:101:5:
    assertion `left == right` failed
      left: 2026-07-09T21:15:44.275422Z
     right: 2026-07-09T21:15:44.275422558Z

     thread 'vacate_expired_noop' panicked at examples/tests/lease.rs:276:5:
    assertion `left == right` failed
      left: 2026-07-09T21:15:41.271889Z
     right: 2026-07-09T21:15:41.271889516Z

there is rounding issue at play somewhere, i'll start looking into this tomorrow.

[alpeb]

I've pushed a couple of commits to address the test failures. Also the chrono->jiff changes required in kubert/src/lease.rs introduced potential panics that were addressed as well. Unit tests around that logic were added too.