Spawned from WT-14636. We still need to investigate why MongoDB would return EBUSY due to  WT_UNCOMMITTED_DATA. WT-14852 fixes the problem on MongoDB spill KV engine which works different to classic MongoDB. There is an invariant commented out in SERVER-100890 that causes WT_SESSION::drop to return EBUSY due to the WT_UNCOMMITTED_DATA sub-level error ("the table has uncommitted data and cannot be dropped yet") despite there being no uncommitted data on the table from the application's perspective. In some cases simply retrying the WT_SESSION::drop allows it to succeed, but in other cases retrying the WT_SESSION::drop continues to return EBUSY indefinitely.

This EBUSY uncommitted failure doesn't cause tables an infinite EBUSY loop, and eventually is able to drop the uncommitted table.