Ldap Tests enabled by UnboundID Ldap Server

Deals with https://github.com/Jasig/cas/issues/660

This pull enables ldap tests to execute against an in-memory ldap server backed by UnboundID. The server is first initialized with a common schema, and some CAS-specific objectclasses are registered. Sample LDIF data is then imported into server which primaryli drives the tests. The server is restarted per each test class.

I have had to haul the existing ldap tests to somewhat get them functional with unboundid. Hopefully, the presented structure allows one to easily add/remove tests and to observe CAS-specific behavior, with less focus and attention on ldaptive config itself. Most beans are condenced into a single context file that is shared across test classes. 

The sample data that is imported is mostly designed to get tests working, again with focus on CAS functionality while allowing (and assuming) that ldaptive would handle directory-specific changes, configuration and various schemas. 

Probably, the one class that is most impacted by this pull is the ldap-based service registry that is also tested more heavily than others, in view of the recent changes that were made to the CAS service model. There are small changes here and there, but  the most significant one is probably the addition of the objectclass "top" to the ldap entry that contains the CAS service. 

I'll try to highlight other changes as well throughout the pull.
This exception is stored in the HandlerResult returned from the authentication subsystem. Those objects are passed around fairly liberally. Are we concerned about providing too much information about authentication failures that might leak out to the user?