SSP-1881 harmonize user_name lengths
* Harmonized up_person_dir.user_name to varchar(50)
* Harmonized up_user.user_name to varchar(50)
* Harmonized up_sso_ticket.user_name to varchar(50)
* Harmonized up_raw_events.user_name to varchar(50)
SSP-1888 Remove assertion that requires SSP_CONFIGDIR to be unset

Looks like we don't actually need this because the default property
source ordering in StandardEnvironment is different than what I
thought... JVM properties are preferred over system env vars. So
as long as tests always set the location of SSP_CONFIGDIR as a
system property, our tests should be fine... which they do seem to
be.
SSP-1978 Inject ApplicationContext into PortalPreAuthenticatedProcessingFilter

Avoids problems when initializing that class from the uP shell. In that
usage, PortalPreAuthenticatedProcessingFilter was (by way of its
collaborators) asking PortalApplicationContextLocator for the current
ApplicationContext, but the latter was still being initialized, which
PortalApplicationContextLocator believed to be an error.
[maven-release-plugin] prepare branch ssp-rel-1-4-patches
[maven-release-plugin] prepare for next development iteration
NOJIRA Bump SSP dependency version
SSP-1982 Update SSP clientTimeout response format expectations

Previously was getting a raw int, now gets a JSON object.

Also now defaults to the server-side default timeout if the
clientTimeout API errors out for whatever reason.
SSP-1988 Send force_platform_session_keep_alive=1 when poking SSP API

Forces the SSP API to dirty the platform session when the client-side
inactivity timeout has expired but the user then indicates that she
wants to keep her session alive. SSP session dirtying should happen as
part of the servlet container's normal request handling.
NOJIRA Add license headers
NOJIRA Update NOTICE file
[maven-release-plugin] prepare branch ssp-rel-1-5-patches
[maven-release-plugin] prepare for next development iteration
NOJIRA Bump SSP dep to 2.4.0-SNAPSHOT
SSP-2145 adding STRENGTH permission to ssp entities
SSP-2150 - Upgrade Spring dependencies to latest 3.2.x release
SSP-2050 Experimental removal of problematic person/attr perm check loop

Not sure this is really the direction we want to go. But this comments out
the obviously problematic code block that we know is leading to excessive
PD DAO lookups. For now just want to see what the impact is while we have
NewRelic hooked up.
SSP-1875 Preserve REMOTE_USER and namespace custom SSO ticket param
Revert "SSP-2050 Experimental removal of problematic person/attr perm check loop"

This reverts commit 2da5107b2e946cb9319fdf0c98abd42004f326d8.

Not going to be able to fully vet this for 2.4 and the change was not quite as
impactful as I had hoped, so rolling back.
SSP-2296 Hide and de-permiss reports from SSP_SUPPORT_STAFF by default
SSP-2297 Hide Manage Users from SSP_MANAGER by default