Optionally mount ephemeral storage as RAID0

This can significantly speed up I/O.  Annoying that this doesn't happen
automagically on EC2 instances.
Make sure apt-get doesn't prompt for config info

Installing mdadm for RAID on the ephemeral drives installs postfix, and
without this, it will prompt for how to configure. We don't care how, and we
don't want to bother the user.
Move the RAID config after package installation

We need mdadm to configure RAID, so we do the RAID config slightly later.
Update the example server config with correct ephemeral device names.
Remove a deprecated TODO
Remove a deprecated TODO
Delete local files after uploading to S3
Install mdadm for process_incoming
Add support for optionally enqueuing to SQS
Add support for reading incoming files from SQS
Check to see if the queued files are in S3

This lets us skip files that have already been processed
Display the filename instead of queue name.
Add a launcher to process an SQS queue
Add util methods for connecting to SQS

Previous code did not connect to a specific region, so it was not obvious which
region the queue would be in.

Also add __init__.py so we can import that code elsewhere.
Add aws region when connecting to SQS
Remove aws_util to avoid the dependency on fabric.
Remove aws_util to avoid 'fabric' dependency.
Add the region parameter in a couple more places.
Update launch_telemetry_server.py with heka config

- Add heka configuration per Bug 920696
- Add production config files for prod and secondary servers
- Use queue-based "process incoming"
- Use binary install for node.js (should be much faster)
Add 'fabric' dependency, allow 'name' override.

The "primary" telemetry server needs fabric to fire up the "telemetry-incoming"
service.

Add an optional parameter to override the EC2 instance name (so we don't have
to create a new config file to launch many servers)
Update provisioning logic and production config.