Users are always created enabled on ApacheDS

When Crowd is asked to create an inactive user in a read-write ApacheDS directory, the user is created as active.

The user can then be manually disabled through the UI and the state is persisted across syncs.

The problem occurs regardless of whether the "localUserStatusEnabled" flag is set to true or false (default).

The root cause seems to lie in the DbCachingRemoteDirectory.addUser method. The UserTemplate object is passed in with active set to false, and then the user creation is delegated to the ApacheDS15 directory, which does not support creating inactive users (See CWD-1740), so it creates an active user and returns that. The returned user is then passed into addInternalUser which dutifully creates an enabled user in the local directory as well. It should create a disabled user in the local db cache instead.