Remove support for the no-cache configuration, revert back to maintaining
only a pair of hazard pointers at most (a parent/child pair), rather than
the full stack of hazard pointers (one per level of the tree).
Merge branch 'develop' into no_no_cache
If raw compression is specified, don't check the overflow sizes or split
percentages against the page size, presumably the application knows what
it's doing.   We still calcalate them, because otherwise we'd have no way
to size the buffers in reconciliation.
Rework wording from Sue.
Merge pull request #451 from wiredtiger/no_no_cache

Remove no_cache support.