experimenting with savon instead of handsoap

* it seems actively maintained
* it gives me more control over the underlying HTTP request, which will
  be useful when dealing with OHLs dog of a server

* current thoughts
  * SOAP  (╯°□°）╯︵ ┻━┻
  * the Savon::Model abstraction was useful to play with, but it seems
    to require setting the SOAP header (and our password) and end point
    in code. We need it them to be passed in at run time so we can hit
    different end points with differen passwords
  * the more general Savon::Client abstraction will probably suit us
    better
  * Now that I understand savon's API, I think I might be able to
    replace handsoap and keep the same public API to this gem. At the
    very least the API will be similar
begin converting ShipmentsClient to use savon
restore Shipment class from master
update for ruby2
update shipment code to use savon instead of handsoap
comment settings used to build a savon client
update the shipment number I test with
remove commented code
add the WSDL for the orders endpoint
update OrdersClient to use savon instead of handsoap
update OrderSearch to use new OrderClient API
move common client code into AbstractClient
setup hello calls to use savon
update CHANGELOG
prepare for a 0.10.0 release
typo
Merge branch 'savon'
don't barf on invalid dates
force mechanize to use TLSv1

* to work around incompatability issues between OpenSSL 1.0.1 and F5
  load balancers
the WSDLs should be in the distributed gem