NOJIRA Bump dev version to 1.3.0-SNAPSHOT
SSP-1668 Support case-insensitive usernames

Dependent on https://github.com/dmccallum/person-directory/commit/90a8fb321770513dbec1cc4f96f990ff7ba73235

Essentially applies the config options added by that commit and
copy/pastes some of its code into LocalAccountPersonAttributeDao, which
was already largely a copy/paste of a PD DAO. Also had to make a few
changes to JpaLocalAccountDaoImpl to support the equivalent of
caseInsensitiveDataAttributes in AbstractJdbcPersonAttributeDao.

SSP-Platform will now support case-insensitive uPortal usernames by
default.

This does *not* include any schema migrations to support
case-insensitive db-layer username constraints.
SSP-1759 - new permissions for Caseload Reassignment
SSP-1738 Add merging person dir DAO and clarify docs

Don't want to add custom attribute sources to the list of DAOs in
the cascading DAO. I.e. the existing comments in
personDirectoryContext.xml gave one the wrong idea.

This commit wraps the cascading DAO in a merging DAO and updates
comments to strongly suggest adding custom sources to the latter
rather than the former.
SSP-1669 Display pager nav bar in person search results
SSP-1644 - Remove unused external person-related permissions
SSP-726	
Add SSP_ADMINISTRATOR as a child group of Portal Administrators in
default uP entity config
SSP-1669 Add documentation for PD search wildcarding options
SSP-1466
Simplify the creation of new confidentiality levels
SSP-1669 Configurable persons search wildcarding exclusions

This brings parity with recent work on SSP's PersonDirectory fork
(PERSONDIR-77). Can now set a property in portal.properties to list
the local uP attributes which should not be automatically wrapped in
wildcards when searched on.

This is important for SSP because whenever we search on the SSP_ROLES
attribute we almost always only want exact matches.

Ideally this behavior would be moved "up" into the queries themselves,
because we don't necessarily want wildcarding shut off in all cases.
But this sort of DAO-layer wildcarding and predicate logic enforcement
is common in PD as well (e.g. you specify search term ANDing or ORing
at the DAO layer, not the query layer). And if you really need to, you
can always include explicit wildcards in the search term and those
*will* be honored, regardless of the wildcard exclusion config. (In
SSP you typically wouldn't include explicit wildcards, though, because
you're often searching against multi-valued LDAP attributes, for which
wildcards won't work.)
SSP-1804 Document recent PD-related config features
SSP-1466
Fixed Typo in config
SSP-1809
ESL permission and confidentiality level adjustments
SSP-1809
ESL permission and confidentiality level adjustments
[maven-release-plugin] prepare branch ssp-rel-1-3-patches
[maven-release-plugin] prepare for next development iteration
NOJIRA Bump SSP dep version to 2.2.0-SNAPSHOT
NOJIRA Peg SSP persondirectory fork dep to 1.0.0