TransactionRepresentation has separate timestamps for start and commit

Recent refactorings ended up using the same timestamp for when a
transaction was started to that of when the transaction was committed.
This commit captures a separate timestamp for when the transaction was
started, i.e. when the user started it.

Also lastCommittedTransactionWhenStarted now correctly reports he
transaction id at the point in time when the transaction was started, not
when committed. The reason for that is that the latter is unnecessary
since it's always going to be the previous transaction id, the way
things work now.
Renamed committing to committed

A long overdue rename. A transaction is committed when it's written to the
log. The 'committing' term indicated that was not the case.
Merge pull request #2829 from tinwelint/2.2-split-tx-time-start-commit

TransactionRepresentation has separate timestamps for start and commit
Added utility for checking whether or not an exception contains a certain stack trace element
Add support for the START clause to the new planner

Internally, it uses a hint that does two things:
- serves as a directive to the search strategy to prioritise leaf plans
  that match the START clause
- creates a runtime pipe that will verify that the start points exist
  to match the behaviour of START in the current implementation

Two acceptance tests have been ignored due to bugginess with OPTIONAL
MATCH that is unrelated to this branch.

Signed-off-by: Pontus Melke <pontus.melke@neotechnology.com>