Provide a generic HTTP driver abstraction

There are currently at least two implementations of HTTP drivers, one for the scheduler API and one for the executor API. We are in the process of adding a third one to communicate with resource providers, MESOS-7469.

Instead of implementing the same logic again and again we should instead extract shared pieces into a generic HTTP driver abstraction which we then modify. It seems one major difference would be in the types of exchanges messages.