Initial commit of monolithic deb package files

The files in this commit can build a single debian/ubuntu package
called titan that contains all Titan jars and dependent jars, an
init.d script that controls RexsterTitanServer, a copy of
rexster-console.sh, and an embeddedcassandra config to get started.  I
tested it Ubuntu 12.04 VMs using Vagrant.

Potential areas for future improvement:

* run as an ordinary user instead of root

* depend on the datastax .deb packages and use the jars it provides
  for cassandra instead of duplicating them in our own package

* split the monolithic titan package a set of feature-specific
  subpackages similar to how the maven modules are split --
  titan-cassandra, titan-hbase, titan-es

* use some combination of maven resource filtering and debian
  substvars to eliminate version number repetition; versions numbers
  should only live in pom.xml files

* (maybe) generate debian-formatted changelog from our own changelog

* add titan's wiki documentation to the package under /usr/share/doc

* run lintian and piuparts

* add stub manpages with invocation synopses and referrals to the main
  wiki-generated documentation
WIP rpm/deb packaging commit
Made ES a test dependency in three modules
Add persistit to titan-all distribution
Deduplicated shared (debian|redhat)/payload files

The authoritative copy of these shared payload files now lives in
pkgcommon/payload instead of having one copy in debian/payload and
another identical copy in redhat/payload
Deb/RPM packaging script edits
Moved package tools under maven control

The debian, redhat, and pkgcommon directories no longer live in the
root of the repository.  Instead, they live under
titan-dist/titan-dist-all/src/pkg.  Running "mvn install -Ppkg-tools"
in titan-dist-all will copy the directories into the root.  One file
is currently filtered: pkgcommon/etc/version.sh.  This file contains
Titan's Maven version information; in future commits, I'm going to
update the package build toolchain to use this version information
instead of hardcoding it.
Configure titan-dist-all to clean deb/rpm tools
Fix maven-clean-plugin config for pkg-tools
Specify an exact maven-dependency-plugin version
Collected deb/rpm changes from the past ~3 days

Combination of README files, packaging script bugfixes, and packaging
features
Ignore transient .deb/.rpm packaging folders
Initial Sonar support in pom.xml files

This changeset generates a single JaCoCo coverage file containing the
aggregated coverage data for all Maven modules containing tests.  It
also adds a Sonar plugin configuration that uploads the coverage data
to a Sonar server.  The approach is inelegant, but it seemed to be the
least worst compromise between various tooling limitations.  In
particular, Sonar operates on a per-module basis, and it appears to
discard coverage data for source files outside the module it's
currently considering.  This is a problem for our project, since most
of our tests exercise code across Maven module boundaries.
Stop swallowing InvalidRequestException
Merge branch 'deb-rpm-packaging'

Merging debian and redhat package creation scripts into master.

Conflicts:
	titan-dist/titan-dist-all/pom.xml
Flattened holder class in CacheVertex
Disabling JaCoCo by default
Disable JaCoCo agent on JVM command line
Restore titan "standalone" assembly
Merge branch 'master' into multiquery

Conflicts:
	titan-core/src/main/java/com/thinkaurelius/titan/graphdb/vertices/CacheVertex.java