correct passenger module configuration

RVM-based passenger installation was failing on Debian platforms as
the handling of passenger configuration (delegated to the
puppetlabs/puppetlabs-apache module) did not support apache::mod
-level overriding of module paths; this is required for passenger
installations handled outside the OS package system (i.e. compiled
via "passenger-install-apache2-module").

Changes to this module:
- additional parameters have been added to the the
  rvm::passenger::apache class to support passing through
  configuration to apache::mod
  - the puppetlabs/puppetlabs-apache module is currently referenced
    via its git repository, which supports the additional apache::mod
    parameters; this will be changed back once these updates have
    been released to the puppet forge
- streamlined execution of passenger-install-apache2-module
  - executing based on existence of compiled module
  - streamlined assembling path to compiled module
- fleshing out debian package requirements for rvm:passenger::apache
- spec/classes tests have been updated to reflect revised
  rvm::passenger::apache parameters
- spec/acceptance tests have been updated to more thoroughly verify
  correct installation/configuration and operation of RVM/passenger
  features, including:
  - installation and configuration of rvm, rubies, gemsets and gems
  - installation, configuraation and operation of apache+passenger
  - removing "--binary" requirement for building gems; some defined
    nodes do not are not supported with RVM ruby binaries
  - passing for all nodesets
- fleshing out spec/acceptance setup:
  - install puppet earlier, enabling access to facter within specs
  - adding ubuntu-server-12042-x64 nodeset
- removing no-longer-in-user passenger-apache-* templates
fix scoping in puppetfile

even git-based modules should use organization scoping (when available) to aid dependency resolution
reverting scoping of apache module, due to issues with librarian-puppet double-referencing git-based module; this will be restored to a forge-based module reference soon in any case
updating passenger configuration behavior for compatibility with mod_lib-fixed puppetlabs/apache module; also added spec/acceptance tests for passenger 3.0.x and 4.0.x, incl. a workaround (just in the spec/acceptance tests) for Redhat family OS issues with recent puppet versions
correcting spec_helper_acceptance preinstallation of module dependencies
tweaking passenger setup for more consistent behavior across redhat and debian; passenger_extra.conf is always copied to passenger.conf - corresponding test updates
restore installing jruby to spec/acceptance tests
refactored spec/acceptance/rvm_system_spec for correct rspec usage; correct usage (in particular, moving local variables into lazy-evaluated "let(:foo)" statements) enabled removing the spec_acceptance_helper hacks to pre-install puppet/facter before configuring rspec (i.e. bad rspec usage was the only reason for those hacks), and cleaner spec acceptance test execution
removing the spec_acceptance_helper.rb hacks to pre-install puppet/facter before configuring rspec (i.e. bad rspec usage in rvm_system_spec.rb  was the only reason for those hacks); note that this was meant to be included in the last commit
Update beaker to use docker

Check if image has puppet preinstalled
Can't change the default ruby or puppet fails to run in Docker CentOS
Use 'rvm do' syntax
Disable apache service to ensure applying twice doesn't fail
Can't add host in Docker
Use super() with :let statements
Bump version to 1.6.0