Lock Down Schemas On Admin Endpoints

Admin diagnostic endpoints (all the /search) contain a ton of arbitrary fields. We should figure out which required fields form the rigid api and enforce them in the yaml and unit tests. We should figure out which fields are just good to be able to show, but we don't want to have to maintain changes in. This will require a better understanding of the UI module that is interacting with these endpoints.