Change latest to installed for socorro packages

[jdotpz]

This is meant to address this scenario:

• v1.0.1 is in production, v1.0.2 is in staging being tested/updated
• We scale in a new node into a production cluster
• The new production node has v1.0.1 baked in on instantiation
• Puppet runs on the new production node, upping it to v1.0.2 despite that not being cleared for prod

This will mean we will have to use a base AMI (currently used) for the build instead of querying the AWS API for the latest staging AMI. Otherwise, it would not install the updated version while making an AMI for staging and eventual production.

[phrawzty]

That's a clever solution to the problem - good thinking!

[phrawzty]

Please put a space between the keyword and the fat arrow, i.e.

    ensure => installed

Not sure why the linter didn't catch this.

Same same for the other manifests in this PR.

r+ once this is fixed.

[jdotpz]

Rob has a more clever option actually, which is to only do a package install on the packer run, not the base puppet repo. That seems a bit more ideal.

[phrawzty]

Up to you whether you want to fix and merge or just close, then. I leave it with @rhelmer and you to decide.

[rhelmer]

I think latest versus installed shouldn't make any difference given #86.