Fix for LOGBACK-266 - FixedWindowRollingPolicy MAX_WINDOW_SIZE too small

correct ThreadPoolFactoryBean link to javadocs, correct typo in name of fieldsToCascade field in ComponentDelegate, added receiver function in ConfigurationDelegate (incomplete)

LOGBACK-266 - increase max window size of FixedWindowRollingPolicy to 20.  12 is too restrictive, and the users have voted for it to be increased

make sure that all the 'view as groovy' links work, Gaffer does not support <receiver> at this stage, nor does the translator

This should resolve LOGBACK-749.

throws an exception, attempt to provide the IP address instead.  This
is useful on those systems without a hostname explicitly defined.

made FileAppenderResilienceTest more tolerant, added code wait for compression job in TimeBasedRollingPolicy

In the receiveMessage and receiveWithContext tests, only ten
milliseconds were allowed for the appender to dispatch the message over
the socket.  Practical experience suggests that on the build system, the
actual latency is on the order of hundreds of milliseconds.  I changed
the allowed wait time to 1000 milliseconds.  This should have little
impact on test duration, as the test will finish as soon as the latch
we're awaiting is updated.

The number of iterations for the loop in lateServerLaunch was derived
from the delay allowed for the appender latch.  The new value for the
delay resulted in an iteration count of one.  I changed this test to
simply use a fixed iteration count.