Swift Delete Vault Fixes

JIRA: CBDEUCE-120

- Swift only returns 204 when deleting a vault. Checking for >= 200 and < 300 is not valid
- When deleting a vault, treat 404 as successful b/c it means the container was not found - thus it does not exist
- Added cleanup mechanism to the swift mocking so that it deletes its directories when the module is unloaded
- Improved implementation of swift mocking container deletion to more accurately reflect the Swift Documentation
- Removed extraneous block deltion line (duplicate line)

Note: tox complains about the try/catch mechanism not being covered; however, it is required for connectivity issues that are not presently mocked.
Swift Delete Vault

- Enhancement: Added functionality to test when the swiftclient tosses an exception for any reason
Swift Delete Vault

JIRA - CBDEUCE-120

- Bug Fix: Missing import of os.path from the disk driver
- Bug Fix: Missing test for a deleting a non-existent block
Bug Fix Swift Delete Vault

- pep8 fixes
Swift Delete Vault Bug Fix

- update transaction id to be consistent with other uses
Swift Delete Vault Bug Fix

JIRA - CBDEUCE-120
- Bug Fix: convert UUID to str()
Merge pull request #58 from BenjamenMeyer/bugfix_swift-delete-vault

2 LGTM's - merging
Bugfix swift delete vault
Merge branch 'master' into bugfix_get-file_wrong-content-type

Conflicts:
	deuce/drivers/swift/swiftstoragedriver.py
	deuce/tests/test_disk_storage_driver.py