Added support for clustering

Really route to all resources

OF-812 properly handle start attribute in list requests

OF-593 LocaleUtils: convert dots to underscores

patch by Paolo Manili

patch by Andrea Ratto

OF-807 + OF-670: Prep for 3.10.0

Kick MUC user when a corresponding packet is returned with any permanent
error condition (PacketError.Type.cancel).

Detect "remote-server-not-found" error condition and remove
corresponding MUC users

Initial tests included assertions for post-conditions that were not part
of the official API.

Prior commit used a local default encoding (and broke the build).

Allow international domain names (per RFC 3490).

Per PR review feedback.

Replace standard XSS filter with something more specific to domain name
validation for the S2S server whitelist/blacklist form.

OF-830: Properly handle LDAP search filters

Updated LDAP components to escape special characters in user and group
search filters, including JID (un)escaping where appropriate

OF-421: More cleanup for MINA API changes

Update version number and dependency change for OF 3.10.0 (due to MINA
2.0.x API change)

OF-843: Update Hazelcast plugin

Adjust xmldebugger for changes in the MINA 2.0.7 filtering API

Conflicts:
	build/lib/versions.txt
	src/java/org/jivesoftware/openfire/nio/ClientConnectionHandler.java
	src/java/org/jivesoftware/openfire/nio/NIOConnection.java
	src/java/org/jivesoftware/openfire/spi/ConnectionManagerImpl.java

Updated ConnectionManagerImpl and related to merge recent changes
related to client connection throttling (MaxReadBufferSize)

to property route.really-all-resources is true

Updates include changes for Openfire Session API, plus changes needed to
upgrade to Hazelcast 3.3.1; also some core housekeeping (NPE)

Introduce option to really send to all resources

fix missing bracket

fixed encrypted properties containing xml escaped data not saved correct...

Encrypted properties containing data that needs xml escaping (eg a database password containing '&') are encryped in escaped form but decryption uses them directly. Encrypted properties do not need xml escaping.

Eg:
1. Install an mysql connection with the password 'pass&word'; password is saved as pass&word in properties.xml
2. Launch openfire
-> mysql connection is established correctly and password is now stored in encrypted form.
4. Restart openfire
5. Openfire startup fails due to incorrect database password (pass&word) is used.

Improvement of OF-69: Add "Groups user belongs to" column to the User

Summary page

OF-69: Add "Groups user belongs to" column to the User Summary page

OF-842: Additional properties in User Properties view

OF-754: Lock out user option works incorrectly in some cases