Title: Configuring Clustering on Red Hat JBoss EAP

Describe the issue:

The example configurations (Example 5.5. Cluster nodeOne configuration, Example 5.6. Cluster nodeTwo configuration, Example 5.7. Cluster nodeThree configuration) set the system property "org.uberfire.cluster.autostart" to "true".

===
<property name="org.uberfire.cluster.autostart" value="true" boot-time="true"/>
===

But it causes an issue described in BZ1271898. "false" is the correct value.

As the default value is "false", we can simply remove the line from the configuration.

Comment from Alexandre Porcelli:
===
Today for BxMS there isn’t a case for org.uberfire.cluster.autostart to ‘true'

Anyway… we’re working on this for 7, so we expect to have a different infra for clustering (it means a way simpler infra!).
===

Suggestions for improvement:

Remove <property name="org.uberfire.cluster.autostart" value="true" boot-time="true"/> from the configurations.