[wip] Now with more CFN

[rclark]

Working on adjusting streambot to use CloudFormation more effectively.

cc @jakepruitt

[rclark]

This works! \o/

What we end up with is a system where you basically:

• "Install" Streambot in your AWS account by running a stack which defines two Lambda functions (one builds/puts .env files on S3, one creates mappings from streams to Lambda functions).
• Write your own Lambda-backed services in their own CloudFormation templates, calling on the "installed" Streambot functions as needed via custom CloudFormation resources.

Before merge & major tag

• write some tests
• document build/bundle scripts
• document streambot.template and index.js
• docco documentation build script in package.json?
• readmes

[rclark]

Currently this doesn't actually end up providing a meaningful split between config and code. You just end up replacing whatever your real config is with one config parameter that you have to hard-code: the url for the configuration file.

Going to take another pass on the config utilizing a dynamodb table instead of S3 and see what that looks like. If it works better, I'll then go back to the struggle to document the complications of how to actually use this.