Restore loadapp checking

This problem surfaced when Red Hat QA started installing Grizzly
and hit a regression from Folsom. If something is wrong with
permissions (it may be SElinux, or any other problem), the servers
in 1.8.0 enter a loop, spamming logs with huge tracebacks at a rate
of a one to two each second, depending how many workers are there.
In 1.7.4, the server exited with an error message.

The offending commit is 9efa9be167b972a234ecccd9ba37bdd8a949381e,
"Separate wsgi init from web-front-end activation". It relocates
the probing invocation of loadapp() in front of drop_privileges().
But in such case, it runs as root and thus may succeed while the
rest of the server fails.

The fix is to return loadapp to the place it was in Folsom. Since
the init_request_processor() is used when running under Apache,
preserve that API too.

Change-Id: I166332eb9375229aefed6b9c3ef1a992a3e4efd0
Make sample configs more readable.

Inject some empty lines to avoid the wall-of-text effect and to make
it a little clearer which descriptions go with which options.

Change-Id: I58914b83dad76ea5ca330903a246bee7ffaeba83
Improve config samples

- Add proxy-logging to multinode. We had it since Folsom and people
  still forget it, resulting in missing logs.
- Use correct name, for ease hit with '*' in vi at least.

Admittedly trivial changes, which I meant to hold until Leah's major
doc improvement lands, but I'm tired of keeping stuff like this in
my working repo.

Change-Id: I44f80c51d6d7329a9b696e67fcb8a895db63e497
Merge "Improve config samples"
Merge "Make sample configs more readable."
Merge "Restore loadapp checking"