Supersedes #1075

Fixes #938

cc @CeesKass

Note: this also modifies integration tests to add the test suite name to the connection name. This makes it much easier to know which tests may be having issues by looking at the RabbitMQ logs.

Proposed Changes

While testing my usage of the RabbitMQ.Client library against a blocked RabbitMQ server I encountered an infinitely hanging dispose of my publisher see #938

Types of Changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

• Bug fix (non-breaking change which fixes issue Connection.Abort uses a timeout of infinity by default, potentially blocking Connection.Dispose #938)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause an observable behavior change in existing systems)
• Documentation improvements (corrections, new content, etc)
• Cosmetic change (whitespace, formatting, etc)

I'm not sure if this is a breaking change or not, I did not dive deep enough into the Abort procedure to know if anything can break when calling with a timeout

Checklist

Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask on the
mailing list. We're here to help! This is simply a reminder of what we are
going to look for before merging your code.

• I have read the CONTRIBUTING.md document
• I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
• All tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in related repositories