provides full(er?) support for transactions

Round three! This provides full (as far as I can tell) support in Rails and where tested in Core. I'm not an expert at using Core so I'm not sure if more tests are necessary. I went with a few basic e2e tests to prove that transactions return normal CypherNode and CypherRelationship objects. As far as Rails is concerned, the entire `active_model_spec.rb` e2e file passes when wrapped in transactions.

This ended up being so much easier to implement than expected. [This](https://github.com/neo4jrb/neo4j-core/compare/master...full_tx-alternate#diff-e5434f25d36a06f1cd47250fb886c312R29) is the key. We tell the transactional endpoint to include the REST response along with its default response. By doing that, we end up with an additional hash containing the same data in the same format as we would receive if we weren't using transactions.

With the response modified, it's easy to determine whether a response did or did not come from the transactional endpoint. You find that [here](https://github.com/neo4jrb/neo4j-core/compare/master...full_tx-alternate#diff-667161f645762badf396b66ceecafcb0R75). Along the way, we [add two instance variables](https://github.com/neo4jrb/neo4j-core/compare/master...full_tx-alternate#diff-667161f645762badf396b66ceecafcb0R53) to keep track of how deep in the hash we need to go to find our results.