The system log has become increasingly chatty over time, especially in test environments where debug logging is enabled.  Under certain conditions this may cause interesting log events to scroll out of the RamLog before they can be checked by test scripts.

1. Create a setParameter to define RamLog size.
2. Selectively set this to a higher value in certain resmoke suites where we know ramlog scrolling is likely to occur.
3. Explicitly set this during specific tests where we don't want to increase the entire suite for whatever reason.

While these changes are proposed to resolve testing issues, they may serve to improve experience for end users.