ISPN-3655 Transactional OL should configure RR and writeSkew by default

* This is necessary in order to make sure conditional replace methods behave as expected in transactional caches without extra RR and writeSkew configurations.
* As a result of changing this default behaviour, so tests started failing, mostly because they're designed to use read committed and not do write skew checks. Those tests' configuration has been adjusted accordingly.

The fix is debatable because as shown in tests like OptimisticReplTxTest, forcing optimistic transactions to be repeatable read and write skew result in different behaviours which will need to be both documented and blogged about. The old behaviour can still be achieved but would require writeSkew to be disabled and read committed to be enabled, but it would require manual intervention from the user.