Fix schema file Content-Type handling
Fix schema file Content-Type handling

* The previous approach relied on lower-layer negotiation with an override for
YAML files.

* A better approach is to nullify the result of lower-layer negotiation (by
deleting the `Content-Type` header from the response writer) and then letting
the Golang file server do its thing.

SpirentOrion/luddite