Decide whether we keep the gRPC API?

[shaneutt]

When we originally started this project the dataplane code included a Kubernetes controller that would pull configuration from the Kubernetes API, after the controlplane had updated the relevant resources. We switched to a gRPC API with a push mechanism which was originally intended to be an interim solution to improve the development experience, testing and debuggability (e.g. you could manually push configuration changes from a console, see all the logs in one place, e.t.c.).

The purpose of this task after discussion with @astoycos and @aryan9600 is that we wanted to check back in and discuss whether we want to go back, or we actually want to keep the gRPC API, as there are pluses and minuses to both.