Make a number of changes to administrative tools provided with OpenDS.  These
are all made under the umbrella of issue #994, but there are individual issues
for each change.

- Issue #979 -- Re-order LDAP tool arguments
  When displaying usage information for many of the LDAP tools (e.g.,
  ldapsearch, ldapmodify, etc.), the arguments were not provided in any kind of
  logical grouping.  This has been corrected so that the arguments are listed
  in a more logical ordering.

- Issue #983 -- Add tool description to argument parser
  When displaying usage information for administrative tools, it now includes a
  small summary of what the tool does at the top of the argument list.

- Issue #984 -- Make tool usage more compact
  Previously, the tool usage included a blank line between each argument, which
  made the usage information seem too verbose, especially for tools like
  ldapsearch with a lot of arguments.  This extra space has been removed.
  Also, many of the argument descriptions have been rewritten in an attempt to
  avoid requiring multiple lines.

- Issue #985 -- Wrap long output in administrative tools when appropriate
  Update most of the output for the administrative tools so that it is easier
  to read on 80-column displays.  This primarily impacts error message, and
  cases in which the format of the output is important (e.g., LDIF output from
  ldapsearch) no changes were made.

- Issue #986 -- Eliminate hard-coded strings in tools
  Some of the tools had hard-coded strings used for error and warning messages.
  They have been replaced with localizeable output from the messages files.

- Issue #990 -- LDAP tools don't use trust store password
  The LDAP tools didn't provide any mechanism for specifying the PIN needed to
  access the contents of an SSL trust store.  Some types of trust stores may
  require a PIN to access them, so it is now possible to either directly
  specify the PIN or to provide the path to a PIN file.

- Issue #991 -- Disconnect when running stop-ds shouldn't be an error
  When using the stop-ds script, if the server began shutting down before it
  returned a response to the client, the client would provide an error message
  making it sound like something went wrong.  The output has now been updated
  to indicate that the server is likely in the course of shutting down.

- Issue #992 -- Tool usage should include the tool name rather than the class
  When displaying usage information for the administrative tools, the
  fully-qualified class name for the Java class was displayed, where the name
  of the shell script or batch file would have been more useful.