Introducing CORS support.

This is a minimum viable solution in order to get cors support working in cougar.

It is meant for discussion and to help improve getting to a good enough state to be merged.
Imagine a service with 2 apis
 1) internal (not customer facing) -> this one does not benefit from cors
 2) external (customer facing) -> this potentially benefits from cors

this impl is a catch all.

this may not be a scenario though.....