Adjust four of our command-line tools for more consistent error reporting,
following the pattern of the core command-line programs.

The visible effects are: error messages will now always have the correct
prefix, and an error will always be reported on failure to flush stdout.

* tools/client-side/svn-bench/svn-bench.c,
  (EXIT_ERROR, SVN_INT_ERR): Delete.
  (sub_main): Return a standard Subversion error object and use standard
    Subversion error handling for the most part. Add an exit_code output
    parameter and use this to yield a non-zero code when not returning an
    error. Don't flush stdout here on success.
  (main): Always use the correct program name in the error message prefix,
    always flush stdout here, and always display any errors here.

* tools/dev/svnraisetreeconflict/svnraisetreeconflict.c
  (SVNRAISETC_INT_ERR): Delete.
  (usage, help): Don't exit.
  (sub_main): New, extracted from main(). Don't do tear-down actions --
    destroying the pool, flushing stdout -- before returning. Simplify error
    handling by using the standard ways such as SVN_ERR().
  (main): Just do initilization and tear-down around a call to sub_main().

* tools/server-side/svnauthz.c
  (handle_exit_error, EXIT_ERROR, SVN_INT_ERR): Delete.
  (sub_main, main): Same as for svn-bench.

* tools/server-side/svn-rep-sharing-stats.c
  (help): Don't exit.
  (sub_main, main): Same as for svnraisetreeconflict.


git-svn-id: https://svn.apache.org/repos/asf/subversion/trunk@1544194 13f79535-47bb-0310-9956-ffa450edef68