Added a test that replicates the Rexster integration test environment.

The purpose of the test is to provide a way to sanity check blueprints operations in Rexster without having to execute Rexster integration tests themselves.  By no means is this a replacement for Rexster integration tests, but at least it helps debug problems around blueprints usage with thread pools.

Currently the test fails for orientdb and therefore the test is named as an "untest".
Merged with latest branch
Switched to OrientDB 1.5.0 final
FIxed issues on using OrientDB on different threads. Created a new THREAD_MODE (by default to AUTOSET_IFNULL)
Uncomment the test that simulates Rexster integration tests.
Fixed transactional test cases supporting OrientDB's optimistic tx
Revert "Fixed transactional test cases supporting OrientDB's optimistic tx"

This reverts commit 97cfc1c41d13bdf8ff55db3579351f6c7023d01d.
Applied my last fix but with the original indent (sorry for such mistake)
Revert to old rexster simulation test and include the one recently added that actually passes for orientdb with retries.  for now both will be commented out.
Merge remote-tracking branch 'origin/master'

Conflicts:
	blueprints-test/src/main/java/com/tinkerpop/blueprints/TransactionalGraphTestSuite.java