Tweak Wicket session parameters

[Twan Goosen]

VLO 3.0 is using a very small amount of memory compared to 2.x. Consider tweaking the Wicket session parameters in VloConfig.xml to allow for somewhat more liberal caching.

Current values:

    
    <!-- Sets the maximum number of page instances which will be stored in the application scoped second level cache for faster retrieval -->
    <pagesInApplicationCache>40</pagesInApplicationCache>
    
    <!-- Sets the maximum size (in KILOBYTES) of the File where page instances per session are stored. -->
    <sessionCacheSize>10000</sessionCacheSize>

These are applied in VloWicketApplication in the following method:

private void setupCache() {
        // configure cache by applying the vlo configuration settings to it
        final int pagesInApplicationCache = vloConfig.getPagesInApplicationCache();
        logger.info("Setting Wicket in-memory cache size to {}", pagesInApplicationCache);
        this.getStoreSettings().setInmemoryCacheSize(pagesInApplicationCache);

        final Bytes sessionCacheSize = Bytes.kilobytes((long) vloConfig.getSessionCacheSize());
        logger.info("Setting Wicket max size per session to {}", sessionCacheSize);
        this.getStoreSettings().setMaxSizePerSession(sessionCacheSize);
    }

[Twan Goosen]

Splitting 3.1 milestone. Most open tickets go to 3.2 so that we can have a release on the short term.

[Twan Goosen]

Removing invalid/wontfix/worksforme tickets from 3.2 milestone