forward agent by default, for deploys

should eventually make this configurable
add `fh init` command for a template config

it works sort of like `vagrant init` in that it drops a basic config
down that helps users see what's available as well as includes defaults
that will allow a basic VM to be booted

json's lack of comment support means the template can't really be
commented; we may want to switch formats in the future to allow for a
commented config file
initial apache + passenger support; config restructure

moving to a more consistently nested config structure, so we have
arrays of `freighthop::database::servers` and `freighthop::web::servers`
to drive different pieces.

we're migrating away from passing config options at the top-level init and
letting them flow down. instead we'll let json driven hiera config drive
any specific config tweaks, with sane defaults wherever appropriate.
this lets a user customize things quite a bit, for example setting up a
config where nginx and apache are both present and listening on
different ports and have different web roots.

this thing will definitely break backwards compatibility with older
configs. i'm hoping the config format will settle down soon.
start moving params class defaults into hiera common

this is more proper puppet and doesn't have annoying load order issues