Fixed ERRAI-795: Errai Security doesn't work with JSR-356 WebSockets
Fixed websocket conversation scope tests
Fixed ERRAI-806: Inconsistent behaviour when binding to List<T>
Fixed ERRAI-807: Nested bindings not updated for types in ErraiApp.properties
Fixed issues in Grocery List demo
Bugfix for ERRAI-809

Added Null check for the return value of listFiles().
Added logging for dirs/files that can't be read in ClassChangeUtil
No longer inherit Junit module in ErraiBus

It's unnecessary and causes the remote logger to be active in GWT 2.7
Fixed ERRAI-811: Marshalling a Map containg null keys creates invalid json
Fixed ERRAI-805: PushState support now compatible with GWT 2.7
Convert history token (from # to pushState) if required
No longer strict compile demos (see below for details)

- We no longer inherit GWT's JUnit module which we should
have never done. In GWT 2.7, it will activate the remote
logger by default and it also causes other problems incl.
significantly increased code size:
https://developer.jboss.org/thread/235647

- We inherited it to make strict compiles pass since
errai-bus, errai-ioc etc. contain base classes that
aim to make testing Errai apps easier (i.e.
AbstractErraiTest). These base classes need the JUnit
module and won't strict compile without it. However,
this is not a problem for testing as the JUnit module
is inherited automatically when running GWTTestCase.

- For now, apps that need strict compilation need to
inherit the JUnit module until we provide a seperate
test module and move our test base classes into this
new module.
Removed outdated setup script
Moved all test base classes to src/test/java

- This makes sure applications can compile in strict
mode without inheriting the JUnit GWT module

- To use our test base classes for application tests
the corresponding test-jar has to be included i.e.
<dependency>
  <groupId>org.jboss.errai</groupId>
  <artifactId>errai-cdi-client</artifactId>
  <type>test-jar</type>
  <scope>test</scope>
</dependency>