Currency: Upgrade kube to v2

[aharbis]

Similar to prior: #145

As a side note, we notice that on main gateway-api supports Gateway API v1.4 - however we're currently implementing against v1.2.1. If there's a possibility of getting the kube uplift without v1.4 that would be great, but understand if that's not viable from your end.

For reference, our current (k8s) dependencies are:

k8s-openapi = { version = "0.25", features = ["latest", "schemars"] }
kube = { version = "1", features = [
    "runtime",
    "derive",
    "client",
    "unstable-runtime",
] }
gateway-api = "0.16"

Perhaps worth a separate discussion, but what's the overall plan for currency here in regards to Kubernetes versions (kube and k8s-openapi) and Gateway API versions? It would be ideal not to always need to track against latest Gateway API, since that's a much less stable interface. Similar to how k8s-openapi allows us to select which version of k8s we want, would it be possible to do similar in this crate? (So we can pick up kube and k8s-openapi currency without being forced to upgrade our Gateway API support as well)

[shaneutt]

I was actually in the midst of updating to 2.0.1, but hadn't quite cut a tag yet so good timing.

I've created gateway-api-release-v1.2.x with kube 2.0.1, but with Gateway API v1.2.1 for you. For the moment can you run your test suite using the branch to make sure that's working for you? Let me know, my intention is to tag yours as 0.17.0, and then follow it up with 0.18.0 which will be on Gateway API v1.4.0.

Going forward, I'll add some process around releasing so this is more formal.