(#22350) Adding a read database, useful for Postgres Hot Standby clusters

Postgres supports Hot Standby: http://wiki.postgresql.org/wiki/Hot_Standby which
uses one database for writes and another database for reads.  This commit adds that
features and some tests ensuring the isolation of the read database calls from
the write database calls
Wrap the two-db shutdown call in a with-connection to ensure the correct
connection is used when shutting down an hsql instance
Change the max # of db connections to 25 per pool, 25 for reads, 25 for writes
Removed indexes that are duplicated by table constraints
Operation Snowmelt (standardize packaging for acceptance)

This commit fixes up our acceptance test code to be compatible
with the "official" packaging API that is now supported by
our release team.
Merge pull request #693 from puppetlabs/operation-snowmelt

Operation Snowmelt (standardize packaging for acceptance)
Merge remote-tracking branch 'origin/1.5.x'
Merge pull request #685 from senior/ticket/master/22350-separate-read-db

(#22350) Adding a read database, useful for Postgres Hot Standby clusters
(PE-1450) Query paging tests for events
(PE-1450) Query paging tests for reports
(PE-1450) Query paging tests for event-counts
(PE-1450) Query paging tests for nodes
(PE-1450) Query paging tests for facts
(PE-1450) Query paging tests for fact-names
Merge pull request #696 from shakedown/dev/1.5.x/pe1450-additional-paging-tests

Dev/1.5.x/pe1450 additional paging tests
Add missing docs for soft_write_failure for master/agent setup

We had added the feature for soft_write_failure in 1.5.x, but the documentation
was only updated for puppet apply cases. This patches updates the documentation
for puppet master/agent setups as well.

Signed-off-by: Ken Barber <ken@bob.sh>
Validate against strings not keywords
Fix precondition in `validate-order-by!`
Resources query paging tests
Sort results during post-processing