(maint) have beaker tests use the host.hostname instead of host.name

-  when you want the current hostname use host.hostname, for some
   provisioners host.name is the name provided by the user but the
   current hostname is generated on the fly and thus different.
Merge pull request #915 from anodelman/beaker-1.5.x-hostname-mistmatch

(maint) have beaker tests use the host.hostname instead of host.name
Merge branch '1.5.x' into 1.6.x

* 1.5.x:
  (maint) have beaker tests use the host.hostname instead of host.name
fix storeconfig export for array values

For exported Resources with parameters which value is a Array the storeconfig export fails to collect them. Instead of collecting all the parameter values into a array it simply override the value with each value in turn.
Added tests around exporting storeconfigs with resources containing
arrays for param values.

Also added activerecord and sqlite to the Gemfile (currently the
storeconfigs tests are not running because those dependencies are missing).
Merge pull request #920 from senior/ticket/1.6.x/pdb-518-storeconfigs-export-arrays

(PDB-518) Fixing storeconfig exports containing arrays
Only pull in activerecord and sqlite3 on new versions of Ruby (1.9.3). This will cause
the storeconfigs spec tests to only run on newer Rubies.
Merge pull request #921 from senior/maint/1.6.x/storeconfigs-tests-only-on-ruby-193

Only pull in activerecord and sqlite3 on new versions of Ruby (1.9.3)
Use ActiveRecord 3.2.x instead of 2.3.x

Signed-off-by: Ken Barber <ken@bob.sh>
Merge pull request #932 from kbarber/maint/1.6.x/use-activerecord-32

Use ActiveRecord 3.2.x instead of 2.3.x
Allow gem source to come from env vars

This will allow CI (among other things) to use a different mirror should
they so choose.