Mark Swift blobstores as eventually consistent

This allows tests to retry correctly.  Most blobstores, including
Swift[1], offer eventual consistency, although Azure[2] and the
jclouds test blobstores offer strong consistency.

[1] https://lists.launchpad.net/openstack/msg06788.html
[2] http://blogs.msdn.com/b/windowsazure/archive/2011/11/21/windows-azure-storage-a-highly-available-cloud-storage-service-with-strong-consistency.aspx
Updated Service Type refs
Update pre-ASF copyright notices
Address Checkstyle violations
Fixes a bug with swift where the metadata is updated, but the content-type is reset to application/x-www-form-urlencoded.

Workaround: send an empty Content-Type header, only for the updateMetadata call.
Prefer Guava HttpHeaders over JAX-RS

jclouds code contains more instances of the former and Guava has
additional constants like CONTENT_MD5.
Revert "Fixes a bug with swift where the metadata is updated, but the content-type is reset to application/x-www-form-urlencoded."

This reverts commit a68c407b414ff361e8201056482134474188770d.
Issue number missing from the commit message.
JCLOUDS-565: Fixes a bug with swift where the metadata is updated, but the content-type is reset to application/x-www-form-urlencoded.

Workaround: send an empty Content-Type header, only for the updateMetadata call.

Re-commit of a68c407b4 with issue number.
Adds a test making sure swift calls will timeout with the right settings.
Adds a mock test to ensure 408 errors are handled properly in swift. This is more likely to happen in swift calls.
JCLOUDS-545: Use established conventions for OpenStack APIs