Consolidate deprecation handling

There were various deprecation handling methods, and this consolidates
them all into a single ActiveMerchant.deprecation method, which also
simplifies the tests.
Give travis-ci a break

ruby 1.9.2 will be EOL next month (June 2014)
and Rails 2.3 is EOL since a while now.

Currently a single commit trigger (4 * 5) - 2 = 38 travis builds
With this change 3 * 4 = 12 builds
Merge pull request #1226 from Shopify/give-travis-a-break

Give travis-ci a break
Authorize.Net CIM: Do not send x_test_request

Closes #1227.
Authorize.Net CIM: Pass delimiter through

Closes #1093.
HPS: Add support for track data

Closes #1225.
HPS: Fix processing without an address

Closes #1229.
Balanced: Do not pass address if zip is blank

Closes #1231.
Do CreditCard attribute cleanup at assignment

The benefit of doing cleanup actively at assignment is that it does not
assume a specific lifecycle for the CreditCard.
eWay Rapid: Add auth/capture/void support
pag_seguro removing excessive whitespace in customer name
Merge pull request #1237 from celsodantas/pag_seguro_name_fix

pag_seguro removing excessive whitespace in customer name
Remove dependency on active_utils Validateable

The goal of this change is to begin breaking the dependency on
active_utils and, in turn, ActiveSupport. We're now doing super simple
validation in ActiveMerchant models, and there's a separate require to
add Rails integration.

For now, using Rails-specific methods without explicitly requiring the
integration will simply generate a deprecation warning. In
ActiveMerchant 2.x the methods will have to be explicitly required.

Closes #1223.
Make all active_utils requires explicit

This makes it easier to see what the dependencies are so we can proceed
to BREAK them.
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.