Stop automatically increasing memory page max

The WiredTiger code currently increases the user-configured memory_page_max value to be at least 50 times a leaf page size. That made some sense when each split created a new internal page, but that is no longer true.

Increasing the user configured value means that users with small cache size can end up pinning the cache full of pages, with no remedy.