Switch to using hazard references for walks through the cache.
Remove the code associated with WT_REF_EVICT_WALK.
Merge branch 'develop' into evict-walk-hazard
Update a couple of comments.
Remove the comments in __wt_bt_cache_op(), they're wrong and it makes
more sense for the discussion to be in __wt_sync_file, anyway.

Remove the WT_PUBLISH of the WT_BTREE.ckpt, it's no longer necessary
because we're not making a request of the eviction server thread.
Rework the initial comment describing different walks.
Set the WT_READ_NO_BUMP flag for compaction, compaction should make a
page more valuable.
whitespace
There's only one remaining verbose hazard pointer message (on
acquisition, we no longer have one on hazard pointer release).
Remove the verbose hazard message, we don't need another test
in the hazard pointer path, and hazard pointer acquisition is
too verbose to be useful anyway.
Fix a comment, there's no "page server" thread.
Merge pull request #886 from wiredtiger/__wt_bt_cache_op

evict-walk-hazard changes
Merge branch 'develop' into evict-walk-hazard
Run voxer tests for 5 hours.
Add a multi-table config and shorter voxer configs for Jenkins.
Adjust thread pools for new Jenkins configs.
Add 1b and 4b test configs.
We can't look at the WT_PAGE_MODIFY.u.m.multi fields unless the
split flag is set for the page.
Take a copy of the update transaction ID in reconciliation in case we race with a rollback.  Go straight to aggressive eviction once the cache gets stuck.

refs #894
Merge branch 'develop' into evict-walk-hazard
[mq]: evict-walk-review
Make a flag so that avoiding forced eviction is explicit, and always on for the eviction server thread.