/etc/boto.cfg, fixes to analysis-worker-stack.yaml, cowboy trick necessity reduction :)

This fixes a few bug in `analysis-worker-stack.yaml` so the user-script actually works...

Then I've changed ` provisioning/aws/create_telemetry_base_ami.py` to call the image what-ever the instance was called... so when you invoke it, you give it the `-n telemetry-base` to generate an AMI called `telemetry-base-YYYYMMDD`. You can also put `telemetry-base` as instance name in your configure file.

The reasoning being that we'll often want to build test AMIs... then we can call them something stupid like `jonasfj-delete-this-soonish`... So we can actually cleanup AMIs we're no longer using... Right now the analysis service uses an independent AMI, but I see no reason it shouldn't use the same AMI as the other parts.

Oh... I ran into some issues with boto not being good a getting credentials from IAM while running on EC2... Turns out you can tune to the number of times boto is allowed to lookup the meta-data service... As a bonus it turns out that we can also get boto do some extra retries for normal requests, like S3... So I just added some retries, 3 (default) wasn't quite enough for me :)

All this boto configuration is done in a `/etc/boto.cfg` so it applies to all users...