Added a regression test for SQS's delete behavior & updated the docs.
Regression test passing, demonstrating ``force_deletion`` no longer has an effect.
CRITICAL FIX

    The teardown method used to delete ALL LOAD BALANCERS in your account.
    Though this is not necessarily a bad thing on its own, it can really
    burn you if you happen to run the integration tests in a staging
    environment that you care about.

    The fix makes all assertions that are based on modifications to load
    balancers refer to the fixture that is created in the setup method.
    There was repeated code that was doing the same thing as the setup
    method--this code also cleans this up.

    NOTE: THIS IS JUST A FIX TO elb/test_connection.py. All of the
    integration tests need to be looked at with this issue in mind.
Merge pull request #1358 from itsdawomb/develop

Don't delete all load balancers when running unit tests for ELB
Merge branch 'sqs-deletion-test' of git://github.com/toastdriven/boto into toastdriven-sqs-deletion-test
Merge remote-tracking branch 'upstream/develop' into develop
Add port to server_name method.

Apparently this is used to create HTTP objects, instead of passing
the port explicitly.
Update test to expect bytes.
Update the text/bytes handling in SQS messages.

SQS message are always unicode, but they have to be converted to/from
bytes to make it through the base64 encoder.