Fix Rails compatibility layer validation messages
Fix rails compatibility flagging
Explicitly require timeout and socket

Fixes fresh test runs under 1.9.3.

Closes #1242.
Balanced: Handle legacy card tokens

Closes #1241.
Braintree Blue: Default verification merchant id

If the merchant has configured the merchant_account_id and they want to
use the verify_card option, they probably want that verification run
against their configured merchant account, since Braintree Blue allows
for multiple merchant accounts. This sets a smart default for
verification_merchant_account_id, while still allowing it to be set
independently.

Closes #1244.
Braintree Blue: Kill expected to fail remote tests

They were really testing Braintree internal validations, which are out
of scope for the AM tests.
Extract integrations into an offsite_payments gem

A shim is used to allow existing consumers of integrations to
(hopefully) see no issues.

Closes #1239.
Remove defunct Samurai gateway
Drop stated/tested compatibility with Rails < 3.2

Until we can unhitch ourselves from Rails train completely, we will
track the severe security Rails maintenance policy (background:
http://weblog.rubyonrails.org/2013/2/24/maintenance-policy-for-ruby-on-rails/).

Technically we're not in compliance with that yet since we do not
support/test against Rails 4.1, but that will come soon.
Fix .travis.yml to refer to correct Gemfile
Remove no longer needed test dependencies
ShipIt
Fix PayWay
Merge pull request #1249 from Shopify/shipit

Changing release process to use ShipIt
Revert "Remove defunct Samurai gateway"

This reverts commit c390deecdfee256a45e9a7d2ee38cf14b987c085.

Conflicts:
	CHANGELOG
	Gemfile_rails40
DIBS Payment Services

This commit is maintained separate until DIBS setup a sandbox.
Code by @maxwhite