Create APIcast Proxy Configuration objects on OpenShift as ConfigMap/CustomResource

[mikz]

Making OpenShift the canonical store for APIcast configuration would help decouple APIcast from the API Manager.

Zync already listens on several events, so it can hook into changes to the proxy configuration and create/update/delete OpenShift ConfigMap/CustomResource. Then that ConfigMap can be mounted as a volume to the APIcast deployment and can be accessed by reading a file.