Update `master` with ForgeRock's Last CDDL Commits for Commons 21.x and 22.x

[Kortanul]

• All of the CDDL commits I could find in the Commons Mailing list archives for master have been imported (280 total). Some of the changes available brought us to Commons 22.x, though most of the remaining portion of Commons 22.x is not CDDL and therefore could not be imported. All of the commits added in this PR were publicly available through the archives. The original messages from which the commits were reconstituted are available for audit, and have been archived here: https://github.com/WrenArchiver/forgerock-notifyr-archive/tree/master/organized_notifications/forgerock-commons/master
• The commits were placed on their own branch based off of ForgeRock's last public master commit (c85c17c), then that branch was merged into a new branch based off of the work I started in September of building-up Commons from source JARs. This was done to ensure we have the most complete copy of Commons 21.x / 22.x.
• I've fixed up several build issues related to orphaned files, subtle bugs, etc, and now everything is building with passing tests, except for the following two exceptions:
  • forgerock-audit-handler-csv continues to fail on the same issue as was identified in https://github.com/WrenSecurity/wrensec-commons/issues/6.
  • forgerock-selfservice-example-ui and forgerock-selfservice-example are failing because org.forgerock.commons.ui:forgerock-ui-user:zip:www:22.0.0-alpha-1 is not yet available (I'll have to work on that next).

In 758804a30fd37a41ef08cfe0d1e10b8a6517e121 on 2017-03-10 (RELENG-105) ForgeRock officially changed licensing on the repo to its proprietary, commercial license. To respect and comply with this change in licensing, no Notifyr notifications for this commit -- or any commits thereafter -- were imported.

[Kortanul]

@siepkes Yes, for now the PGP signatures have not been updated. I will do so when cutting a milestone release.