Add statistics tracking around yield loops

There are some hard to diagnose performance problems, where systems appear to be spinning consuming CPU without doing "real" work. We should add statistics in WiredTiger around any place where spinning might cause wasted CPU.

This will allow us to:

• Better identify contention points in WiredTiger
• Have better confidence that unexplained contention points are outside of WiredTiger