Improve conflict exception message to show if conflict is unexpected

Merge exception (aka OakMergeXXXX) are often expected when concurrent sessions do conflicting writes. But in some occasions, we've seen bugs in oak which also lead to merge exception.

This creates confusion during investigation to isolate if it's an issue in oak or a genuine concurrent conflict.

It'd be useful if the exception message has information to distinguish that.