Optional support for SPA & Lambda@Edge

This 1.1 release:

• adds optional support for SPA (Single-Page Application)
• adds optional support for Lambda@Edge (allow an optional association with a Lambda defined externally to the module)
• correct minor fixes/issues

Minor changes after the 1.0.0 release

1.0.1

Minor changes

Major changes on the CloudFront Origin configuration

The initial version of the module used an S3 origin configuration, with the S3 REST endpoint (for security reasons). A Lambda@Edge was then used to manage redirections. However, as raised by several people, this method breaks index when accessing the alternate domain name.
I chose to return to a more simpler version using the S3 website endpoint (and no Lambda@Edge).

Fixing module dependencies

0.9.2

Fixed domain_name in both origin configuration