Some operations, e.g. schema alter, and verify require exclusive access to a collection. This will throw an EBUSY if live restore has a cursor open on said collection. We should return the sub level error code:{{ WT_CONFLICT_LIVE_RESTORE}} for this scenario.

That way in situations like SERVER-104877, the server will have a better idea of the cause. There is one problem here: How can we know that the exclusive access failed because of the live restore specifically? We may not be able to determine that in which case the sub level error would be a guess and perhaps less useful.