v0.2.0: Introducing `kele-get`

This release introduces kele-get -- kubectl get, the Emacs way
🚀. With kele-get you can interactively specify the kind and name of the
resource that you'd like to get and display its manifest in a separate
buffer. What's more, it supports custom resources right out the gate -- a
long-standing functionality gap in kubernetes-el.

See How-Tos > Usage > Working with
Resources for details and a demo
GIF. It's very much an MVP so there are some rough edges. Please open an issue
for any peculiar behavior that you notice.

Added

• Implemented kele-get for interactively getting and displaying a given
  resource
• Context annotations now display whether a proxy server is currently active for
  the given context
• Implemented interactive functions for per-context proxy server management:
  kele-proxy-start, kele-proxy-stop, and kele-proxy-toggle

Fixed

• Fixed an issue where disabling kele-mode resulted in an error reporting
  unbound slot filewatch-id on kele--discovery-cache
• Fixed an issue where cluster servers with ports,
  e.g. https://127.0.0.1:51134, were not recognized properly
• Fixed an issue where namespace completion candidates failed to populate on
  initial fetch of said namespaces from the Kubernetes API

Changed

• Buffer for contexts' proxy processes are now hidden
• Default value for kele-cache-dir is now ~/.kube/cache; before it was
  relative to the value of kele-kubeconfig-path (and unreliably so)