Turn off autobrief for pages in the documentation, do a pass for naming structure.

--HG--
rename : src/docs/checkpoints.dox => src/docs/checkpoint.dox
rename : src/docs/custom_data.dox => src/docs/custom-data-sources.dox
rename : src/docs/data_sources.dox => src/docs/data-sources.dox
rename : src/docs/config-file.dox => src/docs/database-config.dox
rename : src/docs/error.dox => src/docs/error-handling.dox
rename : src/docs/tune-compress.dox => src/docs/tune-compression.dox
rename : src/docs/tune-system-buffer.dox => src/docs/tune-system-buffer-cache.dox
rename : src/docs/tune-huge-page.dox => src/docs/tune-transparent-huge-pages.dox
__wt_lsm_manager_free_work_unit doesn't return an error, and its callers
don't check, switch to void, minor KNF.
whitespace
__wt_lsm_free_chunks() and __wt_lsm_bloom_work() can both fail and
return an error.
A few more minor lint/KNF tool complaints.
Initialize entry, lint thinks it might be used uninitialized in an error
path. (I don't see it, I think lint's wrong, but paranoia now might keep
us from getting in trouble after some future change.)
whitespace
Merge pull request #1184 from wiredtiger/doc-cleanup-autobrief

Turn off autobrief for pages in the documentation, do a pass for naming structure
Handle an illegal value by returning an error, Coverity #1233093 is
worried the default switch case will leak allocated memory.
Coverity #1129036 thinks we can get out of this code without unlocking
the cache_pool_lock.  I don't see it, but maybe Coverity is getting
confused by the name change?  Switch to initializing the local variable
before acquiring the lock, set/clear the is-locked variable in a couple
of places where there's code separating the lock/unlock calls, check the
is-locked variable in one place for clarity.  No real change, in other
words.
The error list source document was renamed, update the script.
bc1119d broke things (we weren't checking __wt_lsm_bloom_work for
an error return, but a simple check for an error isn't quite right,
__wt_lsm_bloom_work returns WT_NOTFOUND if no work is done).  The
only caller of __wt_lsm_bloom_work doesn't care about WT_NOTFOUND,
so remove that semantic, and return 0 if no work is done.  This is
not a complete fix, there's still the EBUSY in #1185.