Implement support for mesos high availability mode

[maximskripnik]

If Mesos is running in the high availability mode, it might redirect to another instance when using HTTP API (which is what this framework will use). The framework should respect that and dynamically change the location of current mesos master (i.e. it should not try to connect to the same master node and follow redirects all the time, but remember that master was moved and send all new requests to the new node).

See: https://mesos.apache.org/documentation/latest/high-availability/#usage:

For HTTP endpoints that only work at the leading master, requests made to endpoints at a non-leading master will result in either a 307 Temporary Redirect (with the location of the leading master) or 503 Service Unavailable (if the master does not know who the current leader is).