Improve performance of the aggregate api server

Currently, the implementation is done in such a way that the api server can cause noticeable slow downs in the k8s api. This results in the api server itself taking >500ms to respond to a request, which seems to be the upper bound of acceptable time in the k8s generic api server implementation. To reduce the number of trace logs generated by that, the efficiency of our REST implementation should be improved.