Add: EFG Environment attribute recipes

We have four application environments:

- staging
- production
- training
- preview

We need to be able to specify in which environment a machine resides.

Based on the environment, we will have a different vhost name,
and thus SSL certs, and database settings.  The database settings
will come from a databag.
Remove: data_bag cookbook is a testing artefact

This cookbook was purely part of a test, and was added
by accident.
Change: virtual host details from attribute
Tidy up commented out code.
Add: Example data bags for each environment

Of course these contain bogus values, and unencrypted values.

This will be fixed shortly - for now they're obviously
bogus.
Add: Get database information from databag

Get database name, username and password from the efg data bag.

Todo: encrypt secrets
Change: Get database.yml values from databag

Machines will only be in one environment, which is set by the
efg_environment attribute.  This will render database.yml using
values from the appropriate data bag.
Fix: Need double quotes to interpolate
Add: vagrant user to test databag

The base cookbook reconfigures sudo such that kitchen converge
won't work because vagrant doesn't have sudo privileges.

Adding a vagrant user in the test databag, with the same groups
and the standard insecure key solves this.
Add: Test databags for each environment

These databags have no serious secrets.
Fix: remove duplicate suite

There were two base suites, one of which used the chef-solo search
cookbook, which isn't needed because we use chef-zero.

Also added a training suite.  No tests, but allows us to verify
that the node correctly converges.
Bumping version
Merge pull request #1 from Atalanta/env-switching

Env switching