Don't treat javax.jcr.InvalidItemStateException as transient during package import

With JCRVLT-547 there was a distinction between recoverable/non-recoverable repository exceptions introduced to allow to fail earlier and also to improve the retry mechanism.

It turned out the javax.jcr.InvalidItemStateException was incorrectly qualified as recoverable exception, as a simple save() later on the same session does never succeed.

There are two different recovery mechanisms in place:

1. Simple retry of the save() on the same session just after few more nodes/properties have been added/modified
2. More complex retry based on checkpoints in the past, where a new session is being used

While 1. is the correct approach for ConstraintViolationException it is never successful for InvalidItemStateException.