Rewriting Titan distro scripts

Replaced titan.sh with a script that starts or stops Cassandra
followed by Rexster with a Titan+Cassandra graph configuration.  Added
Cassandra and Rexster config files and logging config files that write
within the distro's extracted directory.  The new titan.sh can also
delete these data when invoked with the "clear" argument.

This commit is a work-in-progress and should not be packaged or
shipped.  This commit leaves the HBase and BDB distros in a broken
state.  A simplified titan.sh and set of rexster.xml config files is
needed for HBase and BDB.
Customizing imports in zip/tarball Rexster cfg

This shows that we can mirror the customized imports in Titan's
Console.java file in Rexster without modifying Rexster's source or
resorting to an extension.  However, this commit introduces
copy-pasted duplication between Console.java and rexster.xml.  I think
I see a better way to do this now.  The logic in Console.java that
executes groovy import statements should be extracted into a static
method or a method on some new throwaway object.  It will return
groovy code.  A new main method should be introduced to call this
helper method and write the code to a file.  Rexster can then be
configured to execute it via the <init-scripts> configuration option
in the <script-engine> stanza for Gremlin.  It might even be possible
to build this into the titan-dist maven lifecycle, so that it's fully
automated.
Extracted Gremlin imports into utility class

Console.java now relies on a new class, ConsoleSetup.java, to supply a
list of imports/import-statics to execute when bootstrapping a Gremlin
shell for Titan.  The utility class also contains a main method that
writes the imports to stdout or a file.  This is useful for generating
a Rexster <init-script> file for use with Titan that imports all the
same symbols as an interactive gremlin.sh session.  It also avoids
copy-pasting, so that any time we update the import list effective in
gremlin.sh, we will also automatically update the Rexster environment.
Refactored titan-dist and ConsoleSetup

It seems that executing import and import-static statements in a
Rexster <init-script> has no effect on client connections.  The log
shows that the script containing imports was parsed, but the symbols
still don't exist when connecting to the server with
rexster-console.sh.  I already know that the <import> and
<import-static> tags in rexster.xml work for this purpose, so I
refactored ConsoleSetup.java to generate a properties file containing
imports = (comma separated symbols...) and staticimports = (comma
separated symbols...).  This isn't as tidy as using a Groovy
init-script, but it works.
pom.xml changes for titan-dist-* packages
Renamed titan.sh to stack.sh, deleted old files

The files in titan-all/src/ have been superseded by copies under
titan-dist and are no longer used for anything.  Deleted.
Renamed titan-*.properties files in config

Also added HBase and HBase+ES configs copied from bin
Change log4j configuration in titan-all distro

Now the Cassandra process reads from conf/log4j-cassandra.properties
and the Rexster+Titan process reads from
conf/log4j-rexstitan.properties.  These processes write to both stdout
and to the files log/cassandra.log and log/rexstitan.log.

Also deleted the obsolete script titan.bat which still tried to start
the recently-deleted RexsterTitanServer main class.
Remove bin/*.local files from distro archives

This commit deletes some Titan configuration files from the bin
directory of zip/tar archives built by titan-dist and its submodules.
In lieu of these unusually named files in the bin directory, an
expanded set of config files copied from the /config directory of the
repo is now copied to the /conf directory in the zip/tar achives.
Modfiying rexster log4j path

Doesn't seem to be working... Rexster might be overridding the
command-line log4j config at runtime...
Renamed stack.sh to titan.sh
Reorganizing titan-dist src/assembly directories
Moving rpm/deb packaging files into titan-dist
Added quickstart and persistit distros
Moving titan-dist-* submodules into their parent

I'm trying to reduce the number of archive modules in Titan.  We had
almost as many as we did actual source code modules, spreading out our
distro-related files over a painfully disordered directory structure.
Trying to centralize everything in a single module using profiles in a
way that won't break the release plugin.  Not well tested.
Revert "Moving titan-dist-* submodules into their parent"

This reverts commit 09f33171c3601018926a094f6a5cd0ad91a37e8a.

The previous commit tried multiple profiles with different dependency
sets in the same pom.xml, with the intent that each profile's
execution would get evaluated using only its dependency set.  This is
futile when multiple profiles are active at the same time.  All of the
profiles' dependencies are merged into a single set shared across all
profile executions.  I don't see a way to have different dependency
trees in the same execution of a single pom.xml, so I'm reverting back
to lots of distro submodules.
Adding ES config to quickstart distro
Add perf test @Category to several superclasses
Forcibly add empty logfile stubs

I tried to add these in an earlier commit, but I think they were
ignored due to .gitignore and the fact that I didn't specify the -f
option to git-add.
Add confirmation prompt to `titan.sh clean`