Add xml parsing to s3 website module
New methods to get and set website configurations

The following methods are defined:
- get_website_configuration_xml
- get_website_configuration_obj
- set_website_configuration
- set_website_configuration_xml
Fixed typos.
Log request params in _mexe
typo in dynamodb tutorial
mod utils.py:get_instance_metadata allowing access to dynamic data
Abstracted some of #1383 & added tests.
Made the tests comply with 80 char lengths per @jamesls's request.
code example is meant to handle zones not regions
Merge pull request #1400 from rayrayson/develop

Fixed typos.
Merge pull request #1402 from numerodix/develop

typo in dynamodb tutorial
Merge remote-tracking branch 'upstream/develop' into develop
Merge branch 'nathan11g-website' into develop

* nathan11g-website:
  New methods to get and set website configurations
  Add xml parsing to s3 website module
Merge branch 'toastdriven-instance-metadata-urls' into develop

Closes #1406 and #1383.

* toastdriven-instance-metadata-urls:
  Made the tests comply with 80 char lengths per @jamesls's request.
  Abstracted some of #1383 & added tests.
  mod utils.py:get_instance_metadata allowing access to dynamic data
Set 70 second default socket timeout for httplib
Added docs on what an example ``.boto`` file should look like.
Merge pull request #1411 from toastdriven/config-file-docs

Added docs on what an example ``.boto`` file should look like.
Cleaned up & committed @jamesls's "Getting Started" guide.
Merge pull request #1413 from toastdriven/getting-started-guide

Cleaned up & committed @jamesls's "Getting Started" guide.
Make subscribe_sqs_queue idempotent

This patch changes the sid from being a random UUID4 string to an md5
hash of the combined topic & queue ARN.  Since the Sid is now a known
value we can check to see if a Statement with the given Sid already
exists.  If it does, do not add it again.

The reason for this is that as subscribe_sqs_queue is it isn't
idempotent.  It will add the same statement (with a new Sid) repeatedly
until you hit the limits of the SQS Policy (20 statements, 8192 bytes).