Validate configuration before storing it

Although ConfigurationBuilder does some validation, sometimes it needs something more. As an example, the cross-site replication needs a running Transport to check if xsite is really supported.

As a side effect, the console is broken when you try to define the following cache without RELAY2 being present in the JGroups stack.

<infinispan>
<cache-container>
<distributed-cache name="xsite">
<backups>
<backup site="site2"/>
</backups>
</distributed-cache>
</cache-container>
</infinispan>

This happens because the Configuration is stored and the Cache with the exception is stored as well.

The fix proposed it adds a method to ModuleLifecyle where the Configuration can be validated before it is store in the "global state".