DoesNotExist and AlreadyExists are not always properly thrown from the JPA storage

Should renovate how the "DoesNotExist" and "AlreadyExists" exceptions are thrown from the JPA storage impl. Instead of relying on unique key constraints, it should instead select the entity being updated or created first. Done in a Tx this should work well.