Bump elasticsearch to 1.2.1, lucene to 4.8.1, spatial4j to 0.4.1

Note this explicitly enables dynamic scripting, which was disabled
in ElasticSearch 1.2.0. This is needed in order to remove fields.
The reasoning behind this change can be found in
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-scripting.html#_enabling_dynamic_scripting.
add Solr indexing backend.
merge Lab41 Solr integration
Global:
* Remove duplicate httpcomponents from pom.xml
SolrIndex/GeoToWktConverter:
  * Change StorageException to BackendException
  * Implement missing restore/getFetures methods
  * fix mutate and query methods to support multiple cores
add TTL support for Solr (document level)
add LBHttpSolrServer support for SolrIndex
change store1 to use managed schema
Merge branch 'titan05' into lab41-solr
Merge branch 'titan05' into lab41-solr
Updated pom to 0.5.1-SNAPSHOT
Migrated BerkeleyJe based integration test into respective index backend modules. Removed duplicate MAX_RESULT_SET_SIZE configuration option from SolrIndex.
Minor formatting change
fix solr.home to work correctly when run directly from maven
Make titan-es reuse cassandra & bdb test artifacts
Tweaking titan-solr bdb & cass tests

The BDB- and Cassandra-backed tests of Solr introduced in this commit
don't pass.  There are still problems possibly related to
core/collection and field definition that fail the tests.  We may need
to modify or expand the schema files in titan-solr/src/test/resources,
or tweak the test code to use them correctly.

This commit also changes the default for SolrIndex.ZOOKEEPER_URL.  The
old default caused parse errors -- it seems like, despite the name and
default, the way the value is used in the code calls for a
comma-separated list of ZK quorum hosts.  Not sure on that change,
might have to revisit it.
Reinstated commented out test cases, added TEXTSTRING mapping type, simplified documentation around text/string mapping.
Fixed setting custom tx metrics prefix in documentation
Update reference to old "autotype" setting

Should be schema.default
Intermediate index related refactoring to streamlining semantics and index backend interaction.
Check cluster.partition in part vlabel creation

VertexLabelMaker now checks that cluster.partition is true in the
graph configuration when it creates a label with `partition()`
enabled.  Part of #706.

This makes the related cluster.partition check in
`StandardTitanTx.addVertex` redundant for new installations, though
0.5.0 installs could have defined a partitioned vertex label on a non
cluster.partition'ed backend.