[v17] Reissue kube certs when assuming access request

[gzdunek]

Backport #50553 to branch/v17

changelog: Assuming an Access Request in Teleport Connect now propagates elevated permissions to already opened Kubernetes tabs

[ravicious]

changelog: Assuming an access request in Teleport Connect now refreshes open Kubernetes sessions

I think this might not be clear enough to end users who don't know how Connect works behind the scenes. "Kubernetes session" sounds like it might mean kubectl exec --stdin --tty foo -- /bin/bash and then one might wonder what it means for it to be refreshed.

We screwed up a bit by not using the term "local proxy" or at least "gateway" in the UI right from the start – we have no good terminology to refer to what a local proxy is.

How about something like this?

changelog: Assuming an access request in Teleport Connect now propagates elevated permissions to already opened Kubernetes tabs

I looked at the original issue to better understand what kind of language might be more understandable for end users.

[gzdunek]

Makes sense, thanks.