OF-889: Added try-catch blocks to the various JSP pages where Session.getHostName or Session.getHostAddress is called to prevent the Sessions tab from showing UnknownHostExceptions when there are bad client sessions laying around

Update the REST API plugin to version 1.1.1

See http://docs.oracle.com/javase/8/docs/technotes/guides/jndi/jndi-ldap.html#pooling

LDAP Connection Pooling is disabled when using a custom ssl socket. The custom
socket was used to accept unsigned/untrusted/expired ssl certs. I removed the
use of the custom socket, and also added the required system property to enable
connection pooling when using SSL, which was missing.

- Reworked file transfer event handling
- Fixed spelling in API (as this change already broke API backwards compatibility).
- Updated ClientControl plugin to reflect these changes.

OF-922: Revert MINA to 2.0.7

The inputClosed method was added during troubleshooting for MINA 2.0.9
and can be removed now that we have downgraded to 2.0.7.

Rollback of this commit for OF-421:
https://github.com/igniterealtime/Openfire/commit/89c06a88d75e15d36ce7f6ace88bbf5c71fb08df

OF-919 Update bundled jDTS driver to 1.3.1

Seems to have been left as the Impl class rather than the Interface itself.

Not included in the original PR, and to my shame I hadn't noticed.

Fix filter ordering and admin console NPE

OF-913 Treat lib/log4j.xml as a config file in installers

Make module loading driven by a file

OF-477 Correct SASLserver to use consistent digest-uri

Deprecate the User Service and MUC Service Plugin.

Addressing DIRMINA-1012

Where ioSession.getRemoteAddress() returns null, this can cause an NPE.

Private Storage should return an error if feature is disabled

Update the REST API plugin to version 1.1.0

OF-892: Adding Admin panel support for mutual authentication.

Order Fastpath Workgroups by Display Name

OF-883: Prevent sending data to known disconnected peers.

By closing a session when the new MINA inputClosed() handler is triggered, we run
the risk of sending data to the peer. As that peer is known to be dead, this is
pointless (and potentially dangerous - deadlocks have been observed that are likely
related to this scenario).

To prevent sending data during session closure, the close() method has been
overloaded with an argument that indicates if the peer is known to be dead. When
set, its implementation will not attempt to send data.

OF-910 - Error stanzas to MUC room should remove occupants

Currently, only stanzas containing errors of type cancel will cause the
occupant to be removed, however this doesn't appear to catch and remove many
occupants in practise.

This patch therefore removes occupants from the service on any message or
presence error stanza, irrespective of the error type. IQ stanzas do not
trigger the same response, as these may be due to lack of client support
rather than a vanished occupant.

Two additional fixes that relate to OF-883

The close listeners should not be called from within a synchronized block.

When a connection is closed, several events can be involved (and can be triggered).
Some of these events will attempt to close the connection (if it hadn't been already).
This, at best, least to multiple invocations of close-listeners. At worst, a loop of
close-calls is created.

This commit replaces the two-way boolean that guards closure (isClosed) with a
three-way guard. Now, a distinction is made between between a connection that is
closed, and one that is closing.

Additionally, some null pointer guards have been added, as I've seen those pop up in
my local logs during development.