5. kubectl-kcp: get rid of workspace duality and implement logical cluster path semantics

[sttts]

Implementing UX from https://docs.google.com/document/d/1XJJCr16bg22QuJnQB2W98A-djRTtrLr2JE2IWZUHzJU/edit#heading=h.nn8danthd1ys.

• simplified and complete kubectl plugin to implement the second section in https://docs.google.com/document/d/1XJJCr16bg22QuJnQB2W98A-djRTtrLr2JE2IWZUHzJU/edit#heading=h.nn8danthd1ys.
• removed duality between v1beta1 Workspaces in some virtual workspace path and the ClusterWorkspaces in an org. Now you can do kubectl get workspaces in an org

Based on #744.

[davidfestal]

So you don't manage AuthInfo at all in the current and previous context ?
Afair in previous tests I had done, it might bring some very painful behavior where you cannot bring back the auth used (through a --token override for example) with the previous workspace.

[ncdc]

Yes I think this needs to be carried forward

[ncdc]

Based on @sttts 's comment in Slack

verified that overrides don't affect what is persisted. This is what kubectl itself does too. overrides are only used to tweak a client used by kubectl/the plugin.

👍

[ncdc]

Based on @sttts 's comment in Slack

verified that overrides don't affect what is persisted. This is what kubectl itself does too. overrides are only used to tweak a client used by kubectl/the plugin.

👍