Use the latest 1.x version of beaker

Signed-off-by: Ken Barber <ken@bob.sh>
(packaging)(#21631)Update RPM to use Java 1.7 as the default
(packaging)(#21631)Update Debian packaging to use Java 1.7 as the default
(packaging)(#21631)Update JAVA_BIN for OpenSUSE
PDB-119 Pin to RSA ciphers for all jdk's to work-around Centos 6 EC failures

We're seeing EC cipher failures for Centos 6 boxes, this patch pins the ciphers
to RSA only for all JDK's now to work-around the problem.

Signed-off-by: Ken Barber <ken@bob.sh>
Merge pull request #769 from kbarber/ticket/1.5.x/PDB-119-java-ec-cipher-issues

WIP: PDB-119 Pin to RSA ciphers for all jdk's to work-around Centos 6 EC failures
Merge pull request #767 from kbarber/maint/1.5.x/use-latest-beaker

This patch allows us to use the latest 1.x version of beaker
Merge branch '1.5.x'

* 1.5.x:
  PDB-119 Pin to RSA ciphers for all jdk's to work-around Centos 6 EC failures
  Use the latest 1.x version of beaker

Conflicts:
	src/com/puppetlabs/jetty.clj
	test/com/puppetlabs/test/jetty.clj
Merge pull request #768 from shrug/feature/21631

(packaging)(#21631) Update packaging to use Java 1.7 as the default
Add a migration for historical fact storage

These tables will now house the fact values. This particular migration
is taking place to enable deduplication of fact storage when temporal
configuration is activated and users want to historically store all
fact values.
Make facts, facts_metadata migration portable with HSQLDB
Look at abstracting 'facts' at the record layer

This way all of the respective logic for other records can be hidden
away as common sets of functions such as save, update and delete.
Save a Fact record to the database

Given a Fact record of the form (Fact. name value timestamp certname)
saves it to the database when the (save! ...) function is called on
the record.

This will provide the abstraction required for splitting out the
'command' layer and the 'query' layer, but still providing a
nicer (interfaced) data structure to play with on either side.
Only inserts metadata when a fact (name, value) already exists

This is the first step towards actually getting historical facts
working. To reduce on space utilisation keep the facts database as the
store of name/value pairs and have the temporal reference kept in the
facts_metadata table.
Provide more explicit grouping of tests