To represent a stream ID, Openfire defines the StreamID interface. However,
that interface is hardly used. Instead, simple String representations are used
in most places.

StreamIDs should conform to some specifications (notably: they shouldn't
include XML special characters). An implementation of the StreamID interface
is a good place to enforce specifications like that.

This commit replaces all String-based stream ID representations with an
implemenation of StreamID. For clustering/hazelcast, the serialized string
is still being used to exchange data between nodes (I expect that this allows
older and newer cluster nodes to continue to exchange cache information within
the same cluster).

Also in this commit:
- StreamID implementations check for (and escape) XML special characters.
- Duplicate implemenations of the StreamID interface are removed.

Some code refers to streamID while in reality session IDs are implemented. This
commit does not affect those pieces of code.

OF-836 / OF-941 / OF-777

Various SASL-related changes

Openfire should not need to be restarted after a configuration change for SASL.

The GSSAPI SASL mechanism can be enabled by default. It won't be offered
unless there is a specific gssapi-configuration option present.

Openfire should not offer SASL mechanisms if the JVM has no implementation for them.

The changes for OF-1092 accidentally removed a snippet of code that translates
a non-optional part of the GSSAPI SASL configuration. This commit restores that,
with a difference: the configuration is now checked continuously, intead of just
on server startup. This allows for configuration changes that need not be followed
by an Openfire restart.

OF-1119: Do not depend on ordering of chains

When validating a certificate chain, the provided chain aught to be ordered. If our
own ordering fails, we should use the first certifcate of the (unordered) chain,
instead of failing completely.

Set affiliation to 'none' after removing registration from room.

Fixing NPE in RemoteSession

Fix non-working XEP-0136 for monitoring plugin

Include nickname in actor element when kick a MUC occupant.

OF-1115 Use Java 8 for Debian packaging

OF-1093: Allow for empty/unknown user creation dates.

OF-1118: Don't try to use unsupported encryption settings.

Stored preferences of encryption protocols and/or cipher suites might include
non-supported items. To prevent issues, the list of preferences should be checked
against the currently supported items.

Extending the previous commit, this adds CSRF to a number of high-value target
pages, including user password changing, dleetion, lockout, etc, and also for
the login page (to avoid a class of attack we probably don't care about).

The CSRF mechanism requires manual addition to each form, but has been
design reviewed by Simon Waters (Surevine Ltd).

Reflected XSS in import-keystore-certificate.jsp via the passphrase.

Reported by Florian Nivette of Sysdream.

Adding indexes to PostgreSQL for message search query improvement

The mucdesc parameter of muc-service-edit-form.jsp was reflected unescaped in
the summary view at muc-service-summary.jsp

This was reported by Florian Nivette of Sysdream.

Fixed by escaping on output within muc-service-summary.jsp.

In addition, domain validation was added on input.

Some user providers might not be able to provide a creation date. There's no reason
that the admin page should fail over that.
Note that this commit completes commit 2746a7f4,
which had an correct but incomplete fix for the same problem.

The subdomain parameter in external-components-settings.jsp was reflected
in both cases in the deletion URI as an unencoded parameter.

Originally discovered by Simon Waters, then this case found by Florian
Nivette of Sysdream.

Fix is twofold:

* The parameter is now encoded on output, the deletion URI is now set using
the JSP tags instead of string construction.
* The subdomain parameter is validated on input, making it difficult to inject
script elements etc.

OF-929 prevent ghosts by removing ioSession check

untested by me, just a simple s/7/8/ with the debian build files

Since the release of Openfire 3.9.3, users have reported problems with
"ghost" sessions left on the server. After reviewing the changes that
went into the 3.9.3 release, it seemed the fix for OF-464 may have had
some side effect causing this.

Since Igniterealtime's Openfire was reproducing OF-829, I did a test
whereby the functional changes of Igniterealtime/Openfire#ad08cae9
were reverted.  After 36 hours, there were no ghosts!

This will likely necessitate reopening OF-464.

OF-1089: Send IQ result only after messages

OF-1107 Option to not show email, added readme and changelog

Prevent occasional failure of CheckChainTrustedTest

There's one unit test that occasionally fails. This occurs as a result of an unintended
collision. As part of the test, many certificates are generated and stored in keystores.
The alias used for the entry was based on the hashcode of the public ke of the certificate.
The value range of those hashcodes is fairly small (it has only a couple of digits), which
leads to occasional collisions, causing the test to fail.

This commit replaces the hashcode-based alias with the Base64-encoded public key information.
This ensures that aliases for distinct keys are also distinct, while ensuring that the
aliases for equal keys are equal.

OF-1097: jabber:iq:auth / XEP-0078 disabled by default