v6.0-beta.3

* Changed `splitWhenBiggerThan` property to `rollSize` and added the property to the rolling appenders for consistency.

* Issue **#838** : Fix bug where calculation of written and read bytes was being accounted for twice due to the use of Java internal `FilterInputStream` and `FilterOutputStream` behaviour. This was leading to files being split at half od the expected size. Replaced Java internal classes with our own `WrappedInputStream` and `WrappedOutputStream` code.

* Issue **#837** : Fix bug to no longer try and record set activity events for null activities.

* Issue **#595** : Added stream appender and file appender property `splitWhenBiggerThan` to limit the size of output streams.

* Now logs activity change correctly.

* Add support for checkbox and selection control types to activity descriptions.

* Issue **#833** : The global property edit dialog can now be made larger.

* Fixed some issues in the activity manager.

* Issue **#828** : Changed statistics store caches to 10 minute time to live so that they will definitely pick up new statistics store definitions after 10 minutes.

* Issue **#774** : Event logging now logs find stream criteria correctly so that feeds ids are included.

* Issue **#829** : Stroom now logs event id when viewing individual events.

* Added functionality to record actions against user defined activities.

* Added functionality to show a splash screen on login.

* Issue **#791** : Fixed broken equals method so query total row count gets updated correctly.

* Issue **#830** : Fix for API queries not returning before timing out.

* Issue **#824** : Fix for replace method in PathCreator also found in stroom proxy.

* Issue **#820** : Fix updating index shards so that they are loaded, updated and saved under lock.

* Issue **#819** : Updated `stroom-expression` to v1.4.3 to fix violation of contract exception when sorting search results.

* Issue **#817** : Increased maximum number of concurrent stream processor tasks to 1000 per node.

* Issue **#697** : Fix for reference data sometimes failing to find the appropriate effective stream due to the incorrect use of the effective stream cache. It was incorrectly configured to use a time to idle (TTI) expiry rather than a time to live (TTL) expiry meaning that heavy use of the cache would prevent the cached effective streams being refreshed.

* Issue **#806** : Fix for clearing previous dashboard table results if search results deliver no data.

* Issue **#805** : Fix for dashboard date time formatting to use local time zone.