Separate environment configuration

[de-code]

Currently dev, ci and prod are using the same configuration.
Consider separating them.

[de-code]

@giorgiosironi we could just create separate buckets with just some example files which would be fairly straight forward to do I think (just need to have that reflected in the app.cfg). There is always the chance that one of the real latest XML dumps cause an issue but hopefully wouldn't usually happen.

[giorgiosironi]

How shall these buckets be named? We use {environment}-elife-* as a prefix, I can create them in the same builder configuration where peerscout defines the DNS entry, the server size, the additional volume, etc.

[de-code]

Yes, that seems fine. I guess just add the peerscout suffix? Obviously in production we're stuck with the existing names. We could also call it {environment}-elife-peerscout-testdata to make it more clear what the nature of the data is? (Happy to follow other naming conventions)

[de-code]

Actually the test data won't be different per environment so could also just use one testdata bucket and use it for anything but production.

[giorgiosironi]

Still needs to fall under the ownership of one of the stacks, so we can default to ci-elife-peerscout-testdata (created by the peerscout--ci stack).

[de-code]

Yes, that would work too. Just didn't fancy managing multiple identical buckets.